From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] new perflow rate control queue
Date: Tue, 05 Apr 2005 22:40:54 +0000 [thread overview]
Message-ID: <425313F6.4010900@dsl.pipex.com> (raw)
In-Reply-To: <20050404152117.6d90635d.lark@linux.net.cn>
Wang Jian wrote:
> Hi Andy Furniss,
>
>
> On Mon, 04 Apr 2005 16:23:30 +0100, Andy Furniss <andy.furniss@dsl.pipex.com> wrote:
>
>
>>>Because this per-flow queue is new, you can add things useful to it.
>>
>>It does look good :-) I'll test when I get time.
>>
>
>
> The attached is the latest. The last one doesn't sync time: queue has a
> variable time slot length; every flow has it own ticks.
>
> This new patch against 2.6.11 sync queue and flows' time. Every new flow
> has it jiffies set to q->jiffies and use that as start. As q->jiffies
> and flow->jiffies increament in HZ step, time is synced. This will
> improved accuracy.
>
> But HZ is too long for token calculation. Sometimes, one of flow borrows
> too much and get no enough penalty, so another flow hurts. But anyway,
> per flow queue provides better fairness in my test, either in
> short time period or long time period.
>
> Looking forward to your feedback :)
It works OK for me - though I would really need it to be variable rate
to use really - but as you say it's designed for your needs.
I noticed that it drops icmp so you need to be careful about what you
send to it.
If you limit connections and use them all up then alive but not always
active connections will get locked out - there is a netfilter connection
limit already.
As you say above it's not always fair - I didn't test that much it
seemed OK apart from if htb limited it ie.
htb rate higher than sum of rates but less than sum of ceils made it
unfair to a flow with smaller packet size.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-04-05 22:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 7:21 [LARTC] new perflow rate control queue Wang Jian
2005-04-04 8:51 ` Patrick McHardy
2005-04-04 9:10 ` Wang Jian
2005-04-04 11:42 ` Andy Furniss
2005-04-04 13:53 ` Wang Jian
2005-04-04 14:39 ` Wang Jian
2005-04-04 15:10 ` Andy Furniss
2005-04-04 15:23 ` Andy Furniss
2005-04-04 15:57 ` Wang Jian
2005-04-05 22:40 ` Andy Furniss [this message]
2005-04-06 4:17 ` Wang Jian
2005-04-06 12:29 ` Andy Furniss
2005-04-06 12:48 ` Wang Jian
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=425313F6.4010900@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.