On 07/11/2012 12:17 PM, [email protected] -> Ben Greear <[email protected]> wrote > On 07/11/2012 08:11 AM, Eric Dumazet wrote: >> On Tue, 2012-07-10 at 17:13 +0200, Eric Dumazet wrote: >>> This introduce TSQ (TCP Small Queues) ... > > I haven't read your patch in detail, but I was wondering if this feature > would cause trouble for applications that are servicing many sockets at once > and so might take several ms between handling each individual socket. > > Or, applications that for other reasons cannot service sockets quite > as fast. Without this feature, they could poke more data into the > xmit queues to be handled by the kernel while the app goes about it's > other user-space work? > > Maybe this feature could be enabled/tuned on a per-socket basis? >
I speculate[1] that sharing of resources between applications, or sockets within applications, can better be done as a separate action, by using either a purely local mechanism like cgroups, or by a mechanism that can use a global service-information daemon like the oldish "trickle" bandwidth manager (still available on Fedora via "yum install trickle") Strictly speaking, only the trickled component would be needed, and could conveniently reside on a router, while the the trickle shared library could be used initially, and retired in favour of the proper local control mechanism. --dave [1. Polite Canadian for "I'm pretty sure"] -- David Collier-Brown, | Always do right. This will gratify System Programmer and Author | some people and astonish the rest [email protected] | -- Mark Twain (416) 223-8968 _______________________________________________ Codel mailing list [email protected] https://lists.bufferbloat.net/listinfo/codel
