Age | Commit message (Collapse) | Author |
|
Should fix "panic: timeout_add: not initialized" reported by danj@
|
|
OK mikeb@
|
|
ok stsp@
|
|
specific part of pf_test_state_icmp(). This worked by accident on LP64
archs as the struct is eight bytes long.
ok mikeb@ bluhm@ krw@ jca@
|
|
|
|
Use the same values hardcoded in sys/dev/acpi/acpi.c where possible.
OK visa@
|
|
swofp_validate_action(), because actions have a different class of errors.
While there update the error type and error variables type to match the
swofp_send_error() prototype.
|
|
since they were not being used and the OpenFlow specification doesn't
mention anything about them.
ok reyk@
|
|
ok reyk@
|
|
|
|
Needed by an upcoming driver.
|
|
when RTF_CONNECTED routes are added to the routing table.
Specify a route priority calculated in the same way when deleting such routes.
Makes route add and delete code paths consistent again.
ok mpi@
|
|
|
|
|
|
|
|
Local var 'up' is never set in ifioctl().
OK mpi@
|
|
|
|
ofp_map.c file.
ok reyk@
|
|
it to limit the amount of installable groups.
|
|
|
|
Cleanup trailing whitespaces from the previous change while here.
|
|
procter@ has noticed that flow control settings survive module change
when they should be forgotten. It became clear that we're overwriting
the selected FC mode with the requested version instead of keeping
negotiated settings. Tested by procter@.
|
|
|
|
Previously only multi-rate fiber modules would disable the TX laser, but
newer Intel driver does it for single rate modules as well. Reminded by
kettenis@, tested by procter@ and Hrvoje Popovski. Thanks!
|
|
|
|
prioritization by IPL.
|
|
calling splsoftnet() recursively.
|
|
Move the corresponding code in in6_pcbselsrc(). This reduces
differences with IPv4 and will help us to get rid of 'struct route*'.
ok vgross@
|
|
ok mikeb@
|
|
32bit integers.
|
|
|
|
intel use xl710 to refer to 40 gig parts (and 20 for some reason),
and x710 to refer to 10g parts. there's allegedly going to be 25g
parts called xxv710.
i havent included the xl722 parts yet.
im naming the devices by the speed and connector rather than going for
actual intel product names like XL710-QDA1 because other vendors will
use the same chips in product with other names.
intel also put the XL710-QDA1 product id on the XL710-QDA2, which is
a good argument not to use product names too.
|
|
ext_free_fn.
ok tedu@
|
|
reducing the local diff in libdrm.
We only handle a single master as xorg privdrop has already occurred at
the point where the ioctls are issued.
|
|
size changes and add more sanity checks for group buckets payload.
|
|
Tested by Hrvoje Popovski and myself.
|
|
Only the rate adaptation algorithm changes, available data rates do not (yet).
Please let me know about any regressions.
In 11a/b/g modes the driver still uses AMRR, so forcing one of these modes
with ifconfig's 'mode' subcommand will serve as a fallback if necessary.
ok tb@ mpi@ kettenis@
|
|
For now, only build mira if the iwm(4) or iwn(4) drivers are also
built since other wifi drivers don't even have 11n support yet.
This limits platforms affected by this change to i386 and amd64.
make release on i386/amd64 platforms tested by tb@ (thanks!)
ok tb@ mpi@ kettenis@
|
|
This algorithm was designed for use with MIMO and Tx aggregation.
This is joint work with tb@, who helped with all the tricky math bits.
Additional help with testing by phessler@, mpi@, and jmatthew@.
I believe this is now ready for wider testing, and for future work to
happen in-tree.
A paper which explains the algorithm can be found at:
http://www.cs.ucla.edu/wing/publication/papers/Pefkianakis.MOBICOM10.pdf
Roughly, this algorithm attempts to keep track of the current "goodput"
(the effective data rate) for each MCS. It converges towards a rate which
gets the most bits per second transmitted with least loss.
Occasionally, frames will be steered to different rates to probe for changes.
(The algorithm does not send frames on its own. It only advances whenever
the driver has sent a frame.)
Time-based probing to adjacent MCS rates occurs periodically.
This is similar to what AMRR does, except that eventually mira will
try out multi-antenna modes as well.
Event-based probing happens when a sudden change in goodput is detected.
I've chosen to make downwards probing fast, and upwards probing slow.
(The paper does not specify such a preference.)
This means it should react quickly to worsening conditions and pull the
rate down (perhaps to the lowest possible rate). It should then raise
upwards slowly on a rate-per-rate basis as conditions improve again.
In my testing this works as intended as I keep moving a laptop outside
and inside the AP's range.
Not linked to the build yet.
ok mpi@ kettenis@
|
|
frames the hardware is able to receive. Use an xT3R device for best results.
This change has not yet been tested on 1T1R devices due to lack of hardware.
ok kettenis@
|
|
This "cleverness" increase the risk of races due to caching and/or
prefetching between the HC and DMA engine. Many of the bug reports
on bugs@ involving memory corruptions in usb_allocmem() should be
easier to diagnose when not avoided with this change.
From Marius Strobl, ok kettenis@
|
|
|
|
|
|
|
|
This was sitting in my tree for many a month and since the introduction
of interrupt threads, the interrupt vs. process context interlock became
irrelevant. Taking uncontended write locks while "cold" doesn't look
like a big deal as well.
|
|
NULL tests.
ok mpi@
|
|
OpenFlow packets: the new DLT_OPENFLOW bpf methods allows to monitor
the communication with a switch(4) device with tcpdump now. The
remaining debugging messages aren't compiled without DEBUG now. On
amd64, this shrinks the switchofp.o object by about 10k by default and
about 8k with DEBUG enabled.
OK rzalamena@
|
|
hardmtu, pick a value of 65435 that leaves space for some
encapsulation and almost a complete max-IP packet. After some
discussion we picked this arbitrary value.
OK dlg@
|
|
This will allow us to extract type informations from DWARF2 sections. It
also makes developer life easier as debug information are now included in
every object.
Resulting kernels will be stripped using strip(1) instead of ld(1).
Kernel build time increases by approximately 10%. However it is still
possible to disable this by defining DEBUG="".
ok kettenis@, bluhm@, natano@, jasper@, reyk@, deraadt@
|
|
If an incoming packet is directly put into the output path, sending
the icmp error packet is never done. As this is basically forwarding,
calling ip_forward() for such packets does everything that is needed.
OK mikeb@
|