it's the output, not ack coalescing (Re: TSO and FreeBSD vs Linux)

[Vijay Singh]

Is that what FLOWTABLE does? Also we need a mechanism to record time spent at various layers in the stack. Luigi has used his own methods but we're lacking something more generic. At work we have some crude tools that use mcount information to indirectly measure costs but they are not reliable and only provide partial information.

Sent from my iPhone

On Aug 14, 2013, at 11:11 AM, Adrian Chadd <adrian at freebsd.org> wrote:

> On 14 August 2013 04:47, Lev Serebryakov <lev at freebsd.org> wrote:
> 
> 
>>  And we should invalidate this info on ARP/route changes, or connection
>> will be lost in such cases, am I right?.. So, on each such event code
>> should look into all sockets and check, if routing/ARP information is
>> still
>> valid for them. Or we should store lists of sockets in routing and ARP
>> tables... I don't know, what is worse.
> 
> .. or per-CPU copies of the ARP table.. ?
> 
> 
> 
> -adrian
> _______________________________________________
> freebsd-net at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"