Re: Loopback and Nagle's algorithm

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Le mardi 12 avril 2011 Ã 13:54 +0200, Jiri Kosina a Ãcrit :
> On Tue, 12 Apr 2011, Adam McLaurin wrote:
> > > It may be caused by an increase in context switch rate, as both sender
> > > and receiver are on the same machine.
> > 
> > I'm not sure that's what's happening, since the box where I'm running
> > this test has 8 physical CPU's and 32 cores in total.
> Have you tried firing up the testcase under perf, to see what it reveals 
> as the bottleneck?
CC netdev

This rings a bell here.

I suspect we hit mod_timer() / lock_timer_base()  because of delack
timer constantly changing.

I remember raising this point last year :

David answer :

I am afraid no change was done...

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at

[Linux Kernel Discussion]     [Ethernet Bridging]     [Linux Wireless Networking]     [Linux Bluetooth Networking]     [Linux Networking Users]     [VLAN]     [Git]     [IETF Annouce]     [Linux Assembly]     [Security]     [Bugtraq]     [Photo]     [Singles Social Networking]     [Yosemite Information]     [MIPS Linux]     [ARM Linux Kernel]     [ARM Linux]     [Linux Virtualization]     [Linux Security]     [Linux IDE]     [Linux RAID]     [Linux SCSI]     [Free Dating]

Add to Google Powered by Linux