From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org, hagen@jauu.net,
msg@google.com, aterzis@google.com, ycheng@google.com
Subject: Re: [PATCH net-next] netem: refine early skb orphaning
Date: Mon, 16 Jul 2012 23:08:55 -0700 (PDT) [thread overview]
Message-ID: <20120716.230855.968922272409923316.davem@davemloft.net> (raw)
In-Reply-To: <20120714145333.2c441166@nehalam.linuxnetplumber.net>
From: Stephen Hemminger <shemminger@vyatta.com>
Date: Sat, 14 Jul 2012 14:53:33 -0700
> On Sat, 14 Jul 2012 15:16:27 +0200
> Eric Dumazet <eric.dumazet@gmail.com> wrote:
>
>> From: Eric Dumazet <edumazet@google.com>
>>
>> netem does an early orphaning of skbs. Doing so breaks TCP Small Queue
>> or any mechanism relying on socket sk_wmem_alloc feedback.
>>
>> Ideally, we should perform this orphaning after the rate module and
>> before the delay module, to mimic what happens on a real link :
>>
>> skb orphaning is indeed normally done at TX completion, before the
>> transit on the link.
>>
>> +-------+ +--------+ +---------------+ +-----------------+
>> + Qdisc +---> Device +--> TX completion +--> links / hops +->
>> + + + xmit + + skb orphaning + + propagation +
>> +-------+ +--------+ +---------------+ +-----------------+
>> < rate limiting > < delay, drops, reorders >
>>
>> If netem is used without delay feature (drops, reorders, rate
>> limiting), then we should avoid early skb orphaning, to keep pressure
>> on sockets as long as packets are still in qdisc queue.
>>
>> Ideally, netem should be refactored to implement delay module
>> as the last stage. Current algorithm merges the two phases
>> (rate limiting + delay) so its not correct.
>>
>> Signed-off-by: Eric Dumazet <edumazet@google.com>
...
> Acked-by: Stephen Hemminger <shemminger@vyatta.com>
Applied, thanks.
prev parent reply other threads:[~2012-07-17 6:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-14 13:16 [PATCH net-next] netem: refine early skb orphaning Eric Dumazet
2012-07-14 21:53 ` Stephen Hemminger
2012-07-17 6:08 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120716.230855.968922272409923316.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aterzis@google.com \
--cc=eric.dumazet@gmail.com \
--cc=hagen@jauu.net \
--cc=msg@google.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=ycheng@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).