General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Best practices for paced TCP on Linux?
Date: Sat, 7 Apr 2012 00:21:38 +0200	[thread overview]
Message-ID: <20120406222138.GB12641@uio.no> (raw)
In-Reply-To: <CAA93jw4ZrRo70uqAG2AOBcXxKmv0T8WFV34rAQSOnVZAk9-6Fw@mail.gmail.com>

On Fri, Apr 06, 2012 at 02:49:38PM -0700, Dave Taht wrote:
> It would be best to get some packet captures from user's streams that are
> complaining of the issue.

I'll try asking some users.

> Most 10Gige network cards have the ability to have multiple hardware queues
> that will do some FQ for you.
> 
> SFQ or QFQ will FQ the output streams. SFQRED or QFQ + something will be
> able to do some level of queue management but not 'shaping', or 'packet pacing'
> 
> However in your environment you will need the beefed up SFQ that is in 3.3.
> and BQL. If you are not saturating that 10GigE card, you can turn off TSO/GSO
> as well.

We're not anywhere near saturating our 10GigE card, and even if we did, we
could add at least one 10GigE card more.

> You can reduce your tcp sent windows.

Do you know how?

> I have a debloat script (with about 5 out of tree versions) that tries it's best
> to do the right thing on home gear and takes a bit of the arcaneness out
> of the mix. I have not got around to trying out a couple algos

But debloat is just like... way too much. And probably not very tuned for our
use case :-)

I'll be perfectly happy just doing _something_; I don't need a perfect
solution. We have one more night of streaming, and then the event is over. :-)

/* Steinar */
-- 
Homepage: http://www.sesse.net/

  reply	other threads:[~2012-04-06 22:22 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06 21:37 Steinar H. Gunderson
2012-04-06 21:49 ` Dave Taht
2012-04-06 22:21   ` Steinar H. Gunderson [this message]
2012-04-07 15:08     ` Eric Dumazet
2012-04-07 15:25       ` Dave Taht
2012-04-07 15:35         ` Steinar H. Gunderson
2012-04-07 15:48           ` Dave Taht
2012-04-07 15:52           ` Dave Taht
2012-04-07 17:10           ` Jonathan Morton
2012-04-07 17:18             ` Dave Taht
2012-04-07 17:44               ` Jonathan Morton
2012-04-07 18:10             ` Steinar H. Gunderson
2012-04-07 18:27               ` Jonathan Morton
2012-04-07 18:56                 ` Dave Taht
2012-04-07 18:50               ` Dave Taht
2012-04-07 18:54                 ` Steinar H. Gunderson
2012-04-07 19:01                   ` Steinar H. Gunderson
2012-04-07 19:08                     ` Jonathan Morton
2012-04-07 19:38                     ` Dave Taht
2012-04-07 20:16                       ` Steinar H. Gunderson
2012-04-14  0:37                       ` Rick Jones
2012-04-07 21:13                     ` Jesper Dangaard Brouer
2012-04-07 21:31                       ` Steinar H. Gunderson
2012-04-07 19:02                   ` Dave Taht
2012-04-07 21:49                 ` Fred Baker
2012-04-07 22:36                   ` Dave Taht
2012-04-07 23:59                     ` Fred Baker
2012-04-07 20:27         ` Neil Davies
2012-04-14  0:35     ` Rick Jones
2012-04-14 21:06       ` Roger Jørgensen
2012-04-16 17:05         ` Rick Jones
2012-04-07 11:54 ` Neil Davies
2012-04-07 14:17   ` Fred Baker
2012-04-07 15:08     ` Neil Davies
2012-04-07 15:16       ` Steinar H. Gunderson
2012-04-14  0:44     ` Rick Jones
2012-04-07 14:48   ` Dave Taht
2012-05-12 20:08 ` Steinar H. Gunderson

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

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120406222138.GB12641@uio.no \
    --to=sgunderson@bigfoot.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.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