[snip]
I bet doing a pre-allocation scheme would be fine. Ie, you make some
guess based on payload size and MSS, allocate those, don't worry if
you allocate too many.
-adrian
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/li
Hi all,
An interesting observation I made last night digging into some pcap
files captured on a server doing TSO/LRO and client side bridge seeing
all packets as they were on the wire...
When doing TSO, the NIC takes the stack supplied template IP/TCP header
and increments the IP ID field for eac
Hi Peter,
On 04/15/15 21:04, Peter Holm wrote:
> Seen during i386 stress tests.
>
> db_trace_self_wrapper(c11e20fc,0,c11b79d4,1eb,e47578e0,...) at
> db_trace_self_wrapper+0x2a/frame 0xe47578b0
> kdb_backtrace(c139e637,2,c120851d,e4757984,e4757940,...) at
> kdb_backtrace+0x2d/frame 0xe4757918
>
We're in the process of migrating our network into the future with 40G
at the core, including our firewall/traffic routers with 40G interfaces. An
issue which this exposed and threw me for a week turns out to be directly
related to net.inet.ip.forwarding and I'm looking to just get some insigh
