From: Andy Furniss <lists@andyfurniss.entadsl.com>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: netdev@vger.kernel.org, bugfood-c@fatooh.org
Subject: Re: Request to include ESFQ patch
Date: Sun, 06 Jan 2008 20:01:40 +0000 [thread overview]
Message-ID: <478133A4.4020903@andyfurniss.entadsl.com> (raw)
In-Reply-To: <20080102155903.M66678@visp.net.lb>
Denys Fedoryshchenko wrote:
> Hi
>
> I took risk and installed ESFQ on my main backbone QoS. I found it highly
> useful, and very need in setup's where is more than 128 flows passing and
> especially where is nat available.
I agree it will be good when it's in.
>
> Here is results with overloaded class for low-priority P2P traffic customers:
>
*sfq was never meant for interactive traffic as such. If you really want
to do QOS for them you would need to (somehow) classify interactive and
give it prio over bulk. I know this may not be practical for your setup,
but what ping times users get will vary depending how many other active
users there are/queue length/how many tcps the user has open etc.
Andy.
next prev parent reply other threads:[~2008-01-06 20:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 16:10 Request to include ESFQ patch Denys Fedoryshchenko
2008-01-06 20:01 ` Andy Furniss [this message]
2008-01-07 4:46 ` Denys Fedoryshchenko
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=478133A4.4020903@andyfurniss.entadsl.com \
--to=lists@andyfurniss.entadsl.com \
--cc=bugfood-c@fatooh.org \
--cc=denys@visp.net.lb \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).