| Age | Commit message (Collapse) | Author |
|---|
|
ok jmc@ schwarze@
|
|
|
|
|
|
|
|
Also, fix a verb-noun mixup; ok jmc@
|
|
in cpu.4.
OK visa@, sthen@, jmc@
|
|
Direct the reader there instead.
ok espie@
|
|
already past the point where development can occur out of the tree.
With this I can successfully scan for access points and tell the chip
to attach to an SSID. RX path should work as well, but since I forgot
to bring the antenna with me to my parents, the reception is a bit
horrible in the metal enclosure.
There are a few reasons this driver is rather big. First we set up the
ARM Cores, uploading the firmware and kicking it off. Then we need to
read all needed information from the registers. Once that is done we
have to set up countless buffers. There are 2 TX rings and 3 RX rings,
plus N TX rings for the actual data that is yet to be implemented.
Merry Christmas!
ok kettenis@
|
|
(If anyone needs a bit more handholding than is in release(8), the faq page
https://www.openbsd.org/faq/faq5.html#Release has more information about
setting this up).
Much simplified from, but inspired by, various diffs from ians@. ok tb@ jmc@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ok deraadt@ phessler@ kettenis@
|
|
|
|
this will be used to replace the bare sleep_state handling in a
bunch of places, starting with the barriers.
|
|
while here, a little less capitalisation
|
|
|
|
|
|
|
|
from lucas gabriel vuotto
|
|
|
|
|
|
support FBT_CREATE. Fall back to FBT_MKNOD + FBT_OPEN so that a valid
sequence of FUSE messages is sent to the file system when creating files.
input from mpi@, otto@
|
|
|
|
|
|
|
|
on exit.
ok mpi@
|
|
From Klemens Nanni.
|
|
if you're trying to free something that a timeout is using, you
have to wait for that timeout to finish running before doing the
free. timeout_del can stop a timeout from running in the future,
but it doesn't know if a timeout has finished being scheduled and
is now running.
previously you could know that timeouts are not running by simply
masking softclock interrupts on the cpu running the kernel. however,
code is now running outside the kernel lock, and timeouts can run
in a thread instead of softclock.
timeout_barrier solves the first problem by taking the kernel lock
and then masking softclock interrupts. that is enough to ensure
that any further timeout processing is waiting for those resources
to run again.
the second problem is solved by having timeout_barrier insert work
into the thread. when that work runs, that means all previous work
running in that thread has completed.
fixes and ok visa@, who thinks this will be useful for his work
too.
|
|
Confirmed on Thinkpad X270
|
|
|
|
|
|
|
|
of Sub::Attribute Perl module.
OK jmc@
|
|
right now the rx ring moderation code makes a decision globally
that a machine is livelocked, and uses that to apply backpressure
on all the rx rings. we're moving toward having the network stack
run on multiple cpus, and fed from multiple rx rings. if_rxr_livelocked
lets a driver apply backpressure explicitely if something tells it
that whatever is consuming previous packets cannot keep up.
while here expose the current ring watermark with if_rxr_cwm.
tweaks and ok visa@
|
|
|
|
|
|
ok kettenis
|
|
struct ifreq and is no longer overloaded with ifr_metric. Moreover,
ifr_index and ifr_llprio were missing and mandoc -Tlint complained
about a "useless macro: Tn".
ok jmc, benno, visa
|
|
no functional change, ie, the output is the same
|
|
ok guenther@
|
|
taskq_barrier guarantees that any task that was running on the taskq
has finished by the time taskq_barrier returns. it is similar to
intr_barrier.
this is needed for use in ifq_barrier as part of an upcoming change.
|
|
|
|
pass in proto icmp max-pkt-rate 100/10
all packets matching the rule in the direction the state was created are
taken into consideration (typically: requests, but not replies).
Just like with the other max-*, the rule stops matching if the maximum is
reached, so in typical scenarios the default block rule would kick in then.
with input from Holger Mikolon
ok mikeb
|
|
|
|
|
