From: Andy Furniss <lists@andyfurniss.entadsl.com>
To: Patrick McHardy <kaber@trash.net>
Cc: Corey Hickey <bugfood-ml@fatooh.org>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [NET_SCHED 00/04]: External SFQ classifiers/flow classifier
Date: Mon, 07 Apr 2008 16:14:14 +0100 [thread overview]
Message-ID: <47FA3A46.20207@andyfurniss.entadsl.com> (raw)
In-Reply-To: <47FA2543.1080609@trash.net>
Patrick McHardy wrote:
> Andy Furniss wrote:
>> --- sch_sfq.c.orig 2008-04-07 11:42:36.000000000 +0100
>> +++ sch_sfq.c 2008-04-07 11:46:41.000000000 +0100
>> @@ -317,6 +317,7 @@
>> q->next[x] = q->next[q->tail];
>> q->next[q->tail] = x;
>> q->tail = x;
>> + q->allot[x] = 0;
>
>
> That might fix the symptom, but I don't think its correct.
> As I said, you can't simply reset to zero since it might cause
> unfairness of bursty flows against non-bursty flows.
I guess it would be nice in some ways to make a drr that has memory but
I think this is a bug.
It was the same pre jhash when perturb was needed so the slots would
change anyway.
If it were intended to be a memory of allot it fails because allot
should never be as wide as +/- 32k (maybe that could be fixed - but only
recently became practical with jhash/no perturb).
Currently a new flow (but not the fist) gets dealt a seemingly random
allot of +/- 32k which means it either gets to monopolise the link until
it has wound down to <=0 or if allot is -ve it gets disadvantaged in the
case that it's packet size is < than the others until its allot has
crept up to 0. If it's packets are MTU size it just gets 1 packet per
round and allot stays -ve.
Andy.
prev parent reply other threads:[~2008-04-07 15:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 17:58 [NET_SCHED 00/04]: External SFQ classifiers/flow classifier Patrick McHardy
2008-01-31 17:58 ` [NET_SCHED 01/04]: Constify struct tcf_ext_map Patrick McHardy
2008-01-31 17:58 ` [NET_SCHED 02/04]: sch_sfq: add support for external classifiers Patrick McHardy
2008-01-31 17:58 ` [NET_SCHED 03/04]: sch_sfq: make internal queues visible as classes Patrick McHardy
2008-01-31 17:58 ` [NET_SCHED 04/04]: Add flow classifier Patrick McHardy
2008-02-01 2:37 ` [NET_SCHED 00/04]: External SFQ classifiers/flow classifier David Miller
2008-02-02 23:23 ` Corey Hickey
2008-02-04 17:48 ` Patrick McHardy
2008-02-04 18:25 ` Corey Hickey
2008-03-29 23:35 ` Andy Furniss
2008-04-01 12:39 ` Patrick McHardy
2008-04-01 19:04 ` Andy Furniss
2008-04-02 11:42 ` Andy Furniss
2008-04-02 12:37 ` Patrick McHardy
2008-04-02 16:26 ` Andy Furniss
2008-04-04 10:42 ` Andy Furniss
2008-04-04 10:45 ` Patrick McHardy
2008-04-04 17:01 ` Andy Furniss
2008-04-04 18:54 ` Andy Furniss
2008-04-07 13:43 ` Andy Furniss
2008-04-07 13:44 ` Patrick McHardy
2008-04-07 15:14 ` Andy Furniss [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47FA3A46.20207@andyfurniss.entadsl.com \
--to=lists@andyfurniss.entadsl.com \
--cc=bugfood-ml@fatooh.org \
--cc=kaber@trash.net \
--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).