General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Daniel Borkmann <dborkman@redhat.com>
Cc: fwestpha@redhat.com, "aqm@ietf.org" <aqm@ietf.org>,
	dclc@irtf.org, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] DCTCP in linux net-next
Date: Fri, 3 Oct 2014 08:46:03 -0700	[thread overview]
Message-ID: <CAA93jw5E6+AkthQ48WCvMeFvkN6NsU4vdynMfZKG6A1YBF1NEg@mail.gmail.com> (raw)
In-Reply-To: <542D05B9.1040601@redhat.com>

The testing on this DCTCP implementation is documented at:

https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=e3118e8359bb7c59555aca60c725106e6d78c5ce

Very Impressive! The use of classification to run this on the same
data plane as other traffic was clever, also...

Me being me, I'd wanted to test it against fq_codel, codel and pie
(all of which support ECN) instead of RED, test it against competing
cc algorithms (what harm could a cubic sender do in an otherwise dctcp
environment?), all of which were impossible given the age of the patch
prior set.

I had no faith in the prior (pre-bql-era) results for DCTCP.

I am also interested in what effects, if any, sch_fq had on the hosts
vs a vs DCTCP. It looks like the code currently falls back to reno,
not cubic, if ecn is not enabled, also...

There are several tests in netperf-wrapper that could be easily
modified to invoke dctcp instead to very rapidly get that sort of
data. (the tests are things like cubic_reno reno_cubic_westwood_lp and
the various tcp_square_wave tests, the 50 flow test, etc)

Regrettably I'm not in a DC environment, I'm still out here, trying to
fix the edge. Hopefully someone(s) else here will re-run their  tests
in with this modernized version of dctcp....

On Thu, Oct 2, 2014 at 12:58 AM, Daniel Borkmann <dborkman@redhat.com> wrote:
> Hi Dave,
>
> [ also Cc'ing Florian as co-author ]
>
> On 10/02/2014 05:20 AM, Dave Taht wrote:
>>
>> I was surprised and delighted to see that DCTCP has now entered the
>> linux net-next kernel (which means it will end up in linux 3.18 if it
>> pans out)...
>>
>> http://thread.gmane.org/gmane.linux.network/332259
>>
>> Benchmarkers fire up yer engines! The last benchmarks of DCTCP were
>> all from the pre-bql era....
>
>
> Indeed, please do. ;) We did longer term measurements in a data center
> environment as attached to the commit message, mostly to provoke incast
> collapse. Results were looking quite promising.
>
>> In similar news, some patches are tightening up BQL. The improvements
>> here are measured in
>> 10s to 100s of us, and in cpu savings...
>>
>> https://patchwork.ozlabs.org/patch/394810/
>
>
> Thanks,
> Daniel



-- 
Dave Täht

https://www.bufferbloat.net/projects/make-wifi-fast

      parent reply	other threads:[~2014-10-03 15:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02  3:20 Dave Taht
     [not found] ` <542D05B9.1040601@redhat.com>
2014-10-03 15:46   ` Dave Taht [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

  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=CAA93jw5E6+AkthQ48WCvMeFvkN6NsU4vdynMfZKG6A1YBF1NEg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=aqm@ietf.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dborkman@redhat.com \
    --cc=dclc@irtf.org \
    --cc=fwestpha@redhat.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