Andi Kleen wrote:
quoted text
> Christopher Snook <csnook@redhat.com> writes:
>> I'm afraid I don't know the TCP stack intimately enough to understand
>> what side effects this might have.  Can someone more familiar with the
>> nagle implementations please enlighten me on how this could be done,
>> or why it shouldn't be?
> 
> The nagle delay you're seeing is really the delayed ack delay which
> is variable on Linux (unlike a lot of other stacks). Unfortunately
> due to the way delayed ack works on other stacks (especially traditional
> BSD with its fixed 200ms delay) there are nasty interactions with that. 
> Making it too short could lead to a lot more packets even in non nagle 
> situations.

How variable is it?  I've never seen any value other than 40 ms, from 
2.4.21 to the latest rt kernel.  I've tweaked every TCP tunable in 
/proc/sys/net/ipv4, to no effect.

The people who would care enough to tweak this would be more than happy 
to accept an increase in the number of packets.  They're usually asking 
us to disable the behavior completely, so if we can let them tune the 
middle-ground, they can test in their environments to decide what values 
their network peers will tolerate.  I have no interest in foisting this 
on the unsuspecting public.

quoted text
> Ok in theory you could split the two, but that would likely have
> other issues and also make nagle be a lot less useful.

Perhaps a messaging-optimized non-default congestion control algorithm 
would be a suitable way of addressing this?

-- Chris
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html