From: Patrick McHardy <kaber@trash.net>
To: David Miller <davem@davemloft.net>
Cc: jarkao2@gmail.com, netdev@vger.kernel.org,
herbert@gondor.apana.org.au, shemminger@vyatta.com
Subject: Re: [PATCH] pkt_sched: sch_netem: Limit packet re-ordering functionality to tfifo qdisc.
Date: Wed, 22 Oct 2008 18:00:06 +0200 [thread overview]
Message-ID: <48FF4E06.8040505@trash.net> (raw)
In-Reply-To: <20081021.163605.57275028.davem@davemloft.net>
[Damn hotkeys for sending incomplete mails :)]
David Miller wrote:
> From: Jarek Poplawski <jarkao2@gmail.com>
> Date: Fri, 17 Oct 2008 22:12:10 +0200
>
>> pkt_sched: sch_netem: Limit packet re-ordering functionality to tfifo qdisc.
>>
>> After introducing qdisc->ops->peek() method the only remaining user of
>> qdisc->ops->requeue() is netem_enqueue() using this for packet
>> re-ordering. According to Patrick McHardy: "a lot of the functionality
>> of netem requires the inner tfifo anyways and rate-limiting is usually
>> done on top of netem. So I would suggest so either hard-wire the tfifo
>> qdisc or at least make the assumption that inner qdiscs are work-
>> conserving." This patch tries the former.
>>
>> Signed-off-by: Jarek Poplawski <jarkao2@gmail.com>
>
> This is an interesting patch.
>
> But the thing that strikes me is this: Why don't we just let sch_netem do
> the reordering inside of itself entirely and just get rid of all of this
> ->requeue() business?
I fully agree, keeping all the ->requeue crap around just for this
cornercase doesn't seem like a good decision. Most of the ->requeue
functions are completely inconsistent in their behaviour anyways:
some undo ->enqueue state changes (which is obviously broken for
netem), some don't, some redo checks from ->enqueue (necessary for
netem), some don't (TBF), ...
next prev parent reply other threads:[~2008-10-22 16:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 9:46 [PATCH 0/6] Add qdisc->ops->peek() support Jarek Poplawski
2008-10-16 12:38 ` Patrick McHardy
2008-10-16 13:08 ` Jarek Poplawski
2008-10-16 22:09 ` Jarek Poplawski
2008-10-17 12:33 ` Patrick McHardy
2008-10-17 13:03 ` Jarek Poplawski
2008-10-17 14:12 ` Patrick McHardy
2008-10-17 20:12 ` [PATCH] pkt_sched: sch_netem: Limit packet re-ordering functionality to tfifo qdisc Jarek Poplawski
2008-10-21 23:36 ` David Miller
2008-10-21 23:51 ` Stephen Hemminger
2008-10-22 5:37 ` Jarek Poplawski
2008-10-22 16:00 ` Patrick McHardy
2008-10-22 16:49 ` Jarek Poplawski
2008-10-22 17:32 ` Patrick McHardy
2008-10-22 17:53 ` [RFC] " Jarek Poplawski
2008-10-22 15:57 ` [PATCH] " Patrick McHardy
2008-10-22 16:00 ` Patrick McHardy [this message]
2008-10-17 20:45 ` [PATCH 0/6] Add qdisc->ops->peek() support Jarek Poplawski
2008-10-21 23:43 ` David Miller
2008-10-22 16:01 ` Patrick McHardy
2008-10-22 16:04 ` Patrick McHardy
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=48FF4E06.8040505@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jarkao2@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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 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.