Age | Commit message (Collapse) | Author |
|
rather than always using RTS for HT protection.
|
|
|
|
helped us on a loaded hackathon wifi network. In 11n mode we are now
using a heuristic for this. Disable RTS threshold for all other modes
again because it can do more harm than good in many situations.
This change may increase Tx throughput in 11a/g modes, though results depend
on the driver. Some drivers, e.g. urtwn(4), keep using RTS regardless for
unknown reasons and may need to be fixed separately. And we will keep using
RTS if the AP enables 11g protection while 11b clients are around.
|
|
|
|
needs the Chain Bit set or not instead of using the last parameter,
which is used to mark the last TRB in a USB transfer, not in a TD.
To make that work we need to setup the recently acquired TRB before
calling xhci_xfer_get_trb() the next time. Thus setting up the
initial TRB has to happen right away. To kick the transfer off we
simply flip the toggle bit on the first TRB right at the end.
Fixes regression for jcs@, dhill@ and stsp@
Initially discussed with mpi@
ok stsp@
|
|
OK yasuoka@
|
|
local and remote address in struct peer changed to bgpd_addrs.
OK benno@
|
|
instead of sockaddr_storage. This again helps protability and simplifies
some code. sa2addr now takes an optional pointer to return the port of
the sockaddr.
OK benno@
|
|
Switch also default-route to a keyword and remove the old 6.3/6.4 announce
compat code.
Reported by florian@
OK benno@
|
|
|
|
Improves throughput and latency on 11n networks.
Tested by myself, jmc@, jcs@, phessler@, benno@
|
|
Problem noticed by jmc@
|
|
libLLVM from a single directory avoid reused filenames by symlinking
duplicated names with a prefix of the component library name so object
file names will be unique.
symlink approach suggested by deraadt@ ok patrick@
|
|
|
|
|
|
matches the result of building with cmake
ok patrick@
|
|
count mbuf load failures as output errors so i can see if that's
a problem (it's not, but at least i can see it isn't now).
|
|
|
|
confirmed by and ok krw
|
|
|
|
IKEV2_CFG_INTERNAL_IP6_DHCP and IKEV2_CFG_INTERNAL_IP6_SERVER by using
the correct member in the iked_addr struct for the address.
From Aram Havarnean
|
|
In the close notify case we need to signal EOF and in the user cancelled
case we need to return WANT_POLLIN. Returning success results in
tls13_record_layer_read_record() thinking that we have record data when
we do not, which then results in the content type check later failing.
ok tb@
|
|
ok tb@
|
|
Otherwise a TLS error (for example the remote end sent a fatal alert) is
silently ignored.
ok bluhm@ tb@
|
|
|
|
OK mpi@ sashan@
|
|
objects that readers can access without locking. This provides a basis
for read-copy-update operations.
Readers access SMR-protected shared objects inside SMR read-side
critical section where sleeping is not allowed. To reclaim
an SMR-protected object, the writer has to ensure mutual exclusion of
other writers, remove the object's shared reference and wait until
read-side references cannot exist any longer. As an alternative to
waiting, the writer can schedule a callback that gets invoked when
reclamation is safe.
The mechanism relies on CPU quiescent states to determine when an
SMR-protected object is ready for reclamation.
The <sys/smr.h> header additionally provides an implementation of
singly- and doubly-linked lists that can be used together with SMR.
These lists allow lockless read access with a concurrent writer.
Discussed with many
OK mpi@ sashan@
|
|
validity for the ca certificate. Raise this from 365 days to 4500 as expiry means
installing new CA certificates on all client machines which can cause significant
pain. This doesn't change the default validity for server certificates which
remains at 1 year (controlled by ikeca.cnf) - refreshing key and certificate
on these can be done easily without visiting all machines. ok deraadt@
|
|
filter_community type is valid. Found while looking into a gcc warning
about uninitialized data.
|
|
|
|
for ANSI escape sequences introduced by an 8-bit CSI (e.g. "\23343m")
because these are neither compatible with UTF-8 nor strictly
compatible with pure ASCII and for those introduced by an UTF-8 CSI
(e.g. "\302\23343m") because not even xterm(1) supports them at
all, not even with a non-default configuration, because both forms
are very rarely used, if at all, and because the current code trying
to support them doesn't even appear to work according to my tests.
Full support for the ESC-[ CSI (e.g. "\033[43m") remains.
Tweaks and OK millert@, OK nicm@,
and sthen@ agrees with the general direction.
|
|
|
|
and setting. This allows rules like:
ext-community * * # delete any ext-community
ext-community ovs * # delete any ext-community of specified type
ext-community rt 1.2.3.4:*
and
ext-community rt 65001:local-as
ext-community rt local-as:11111
Note: Sometimes the type of the ext-community is underspecified when using
wildchars or expands. So 'ext-community rt *' or 'ext-community soo *' will
match for any of the 3 possible types (2-byte AS, 4-byte AS and IP address).
If local-as/neighbor-as is used as an expand of as-number like
ext-community rt local-as:11111
then bgpd will default to the 4-byte AS type to encode the community.
OK benno@
|
|
When disabling the switch, suspending and eventually resuming again with
wifi still off, re-enabling the switch has no effect due to interrupts
being disabled completely.
To ensure seemless operation, explicitly enable interrupts during hardware
initialization iff the switch is disabled.
While here, initialize the interrupt mask up front to avoid clearing the
previously set mask in any case.
OK mlarkin, Feedback and OK ststp
|
|
|
|
From Randy Hartman
|
|
|
|
at the moment there are 256 slots on the right. if rxr raises the
high watermark to 256, we overwrite ring entries.
|
|
this reduces the output that mpw interfaces generate from 3 lines
to the one generic mpls and pwe3 line.
mpw can be configured with the individual ioctls, and gains the
ability to do flow aware transport.
|
|
whether the mpw interface is advertising "ethernet" or "ethernet-
tagged" is something the ends of the wire agree on (ie, ldpd is
configured a certain way), it is not something that affects ethernet
encap or decap.
the MPW ioctls can still configure it and read it, but it has no
bearing on how the driver operates on packets.
|
|
this allows individual configuration of the use of control words,
flow aware tranport labels, and the local and remote label plus
neighbor individually.
discussed with claudio@ at a2k19
ok mpi@
|
|
|
|
the existing mpw ioctl is still available for ldpd to use for a
(short) while.
discussed with claudio@ at a2k19
ok mpi@
|
|
part of a larger diff ok mpi@
|
|
these will replace the monstor mpw ioctl, and will be used by an
upcoming mpls ip tunnel interface driver.
discussed with claudio@ at a2k19
ok mpi@
|
|
makes m_prepend later less likely to allocate a new mbuf.
|
|
this is particularly noticable on sparc64 when you reboot.
ok jmatthew@
|
|
this should give a bit of space if the packet needs an m_pullup.
care is taken to ensure the packet is still aligned for the ip
stack.
ok and tweaks claudio@
|
|
|
|
hopefully it is a bit more obvious that what rw_enter returns can
be passed up to userland.
reads ok jmc@
ok mpi@
|