From: Nandita Dukkipati <nanditad@google.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org, codel@lists.bufferbloat.net,
ncardwell@google.com, David Miller <davem@davemloft.net>,
mattmathis@google.com
Subject: Re: [PATCH v3 net-next] tcp: TCP Small Queues
Date: Wed, 11 Jul 2012 17:46:35 -0700 [thread overview]
Message-ID: <CAB_+Fg5dwsNYkL+rQ4HsrDyHi-3w+EcLjWr0F=HbyLPyXT25AQ@mail.gmail.com> (raw)
In-Reply-To: <1342051233.3265.8206.camel@edumazet-glaptop>
>> Considering these two points, why TSQ over the Codel feedback
>> approach?
>
> I dont think they compete. They are in fact complementary.
>
> If you use codel/fq_codel + TSQ, you have both per flow limitation in
> qdisc (TSQ) + sojourn time aware and multi flow aware feedback.
Makes sense. My conjecture is when using codel/fq_codel qdisc, the
need for TSQ will diminish. But as you said... good part of TSQ is it
limits per-flow queuing for any qdisc structure, even those not using
codel.
next prev parent reply other threads:[~2012-07-12 0:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 15:50 [PATCH v3 net-next] tcp: TCP Small Queues Eric Dumazet
2012-07-11 18:38 ` Andi Kleen
2012-07-11 23:47 ` Eric Dumazet
2012-07-11 19:29 ` Nandita Dukkipati
2012-07-12 0:00 ` Eric Dumazet
2012-07-12 0:46 ` Nandita Dukkipati [this message]
2012-07-12 1:14 ` David Miller
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='CAB_+Fg5dwsNYkL+rQ4HsrDyHi-3w+EcLjWr0F=HbyLPyXT25AQ@mail.gmail.com' \
--to=nanditad@google.com \
--cc=codel@lists.bufferbloat.net \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=mattmathis@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.