From: Dave Taht <dave.taht@gmail.com>
To: Cong Wang <cwang@twopensource.com>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Codel] mesos project adds fq_codel also
Date: Tue, 10 Mar 2015 15:34:05 -0700 [thread overview]
Message-ID: <CAA93jw77kAmuRV7dGrU_sA-C6X-TK07VOj560xv5R3Cr1BGFdw@mail.gmail.com> (raw)
In-Reply-To: <CAHA+R7M_fGejpat5A6aWFHGkRcHuo+CkkFOZSPk4ZAGKBd3XRQ@mail.gmail.com>
On Tue, Mar 10, 2015 at 2:49 PM, Cong Wang <cwang@twopensource.com> wrote:
> On Tue, Mar 10, 2015 at 2:23 PM, Dave Taht <dave.taht@gmail.com> wrote:
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=8b184da431ddf4518691a17eeb75a3ffa04e8603
>>
>> I don't understand how they intend to use it, but....
>
> That is the first commit in a series, the reason is in the last patch:
>
> https://reviews.apache.org/r/31505/
Oh, excellent. I would advocate X queues per container (fq_codel
supports 64k), as 1024 worked well up to 1GigE, but we have never got
good data on 10GigE and above and that might require a bit of testing.
In what sorts of environments is mesos deployed in?
--
Dave Täht
Let's make wifi fast, less jittery and reliable again!
https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
prev parent reply other threads:[~2015-03-10 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 21:23 Dave Taht
[not found] ` <CAHA+R7M_fGejpat5A6aWFHGkRcHuo+CkkFOZSPk4ZAGKBd3XRQ@mail.gmail.com>
2015-03-10 22:34 ` 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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw77kAmuRV7dGrU_sA-C6X-TK07VOj560xv5R3Cr1BGFdw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=cwang@twopensource.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