From: Jonathan Morton <chromatix99@gmail.com>
To: Abas Javadtalab <javadtalab@yahoo.com>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: Re: [Codel] A question about bandwidth sharing with codel
Date: Thu, 13 Feb 2014 07:21:19 +0200 [thread overview]
Message-ID: <F5B72082-3A1D-4A2E-9EBE-95B195089AB0@gmail.com> (raw)
In-Reply-To: <1392267970.84741.YahooMailNeo@web161701.mail.bf1.yahoo.com>
On 13 Feb, 2014, at 7:06 am, Abas Javadtalab wrote:
> I have tested all possible configuration except codel and I will be so thankful if anyone can give me an advice
Codel and fq_codel are essentially plug-and-play qdiscs by design. Why not simply start using them and see what happens?
- Jonathan Morton
prev parent reply other threads:[~2014-02-13 5:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 5:06 Abas Javadtalab
2014-02-13 5:21 ` Jonathan Morton [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=F5B72082-3A1D-4A2E-9EBE-95B195089AB0@gmail.com \
--to=chromatix99@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=javadtalab@yahoo.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