| created | 2023-07-23T19:42:33Z |
|---|---|
| begin | 2023-07-18T00:00:00Z |
| end | 2023-07-19T00:00:00Z |
| path | src/sys |
| commits | 2 |
| date | 2023-07-18T06:58:59Z | |||
|---|---|---|---|---|
| author | claudio | |||
| files | src/sys/dev/pci/drm/drm_linux.c | log | diff | annotate |
| src/sys/dev/pci/drm/include/linux/wait.h | log | diff | annotate | |
| src/sys/dev/pci/drm/radeon/radeon_fence.c | log | diff | annotate | |
| message |
With the update of the sleep API the linux emulation of their wait API, schedule() and set_current_state() can be implemented in a much less hacky way. This should remove some possible race conditions in the wait API. Tested by many (kettenis, jsg, phessler, thfr) OK kettenis@ |
|||
| date | 2023-07-18T16:01:20Z | |||
|---|---|---|---|---|
| author | bluhm | |||
| files | src/sys/dev/pci/if_ix.c | log | diff | annotate |
| src/sys/net/if_loop.c | log | diff | annotate | |
| message |
Enable LRO for TCP per default in the network drivers. Large Receive Offload allows to receive aggregated packets larger than the MTU. Receiving TCP streams becomes much faster. As the network hardware is not aware whether a packet is received locally or to be forwarded, everything is aggregated. In case of forwarding it is split on output to packets not larger than the original packets. So path MTU discovery should still work. If the outgoing interface supports TSO, the packet is chopped in hardware by TCP Segmentation Offload. Currently only ix(4) and lo(4) devices support LRO, and ix(4) is limited to IPv4 and hardware newer than the old 82598 model. If the interface is added to a tpmr(4), bridge(4) or veb(4), LRO is automatically disabled. All ix(4) devices support outgoing TSO for IPv4 and IPv6. Enabling LRO on lo(4) automatically enables TSO and TCP packets larger than the MTU pass the loopback interface. LRO can be turned off per interface with ifconfig -tcplro. OK jan@ |
|||