netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Marcela Maslanova <mmaslano@redhat.com>
Cc: netdev@vger.kernel.org, shemminger@vyatta.com,
	Patrick McHardy <kaber@trash.net>
Subject: Re: [Iproute2]: failed replacing internal netem qdisc with pfifo
Date: Thu, 13 Aug 2009 23:32:19 +0200	[thread overview]
Message-ID: <4A848663.4020304@gmail.com> (raw)
In-Reply-To: <20090813120330.GB7010@ff.dom.local>

Jarek Poplawski wrote, On 08/13/2009 02:03 PM:

> On 13-08-2009 12:26, Marcela Maslanova wrote:
>> Hello,
>> I've received bug report about not being replaced netem with pfifo
>> anymore: https://bugzilla.redhat.com/show_bug.cgi?id=515522
>> This should be possible according to documentation [1].
>> Is this intentional change or is it a bug?
> 
> It's intentional:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=02201464119334690fe209849843881b8e9cfa9f
> 
>> It worked with kernel-2.6.27.5-117.fc10 and iproute-2.6.27. The problem
>> is still present with current iproute and kernel-2.6.29.6-217.2.3.fc11.
> 
> Yes, netem is classless since 2.6.29, so this documentation needs
> updating.


Hmm... I see this is passed to the user as "notabug". On the other hand,
since this functionality looks like useful (and used), I wonder if "we"
weren't too strict, and maybe it should be at least partially restored.
The clasfullness isn't actually a big problem if we skip reordering
(done by putting packets to the head of the queue) for such external
qdiscs. Alternatively we could modify netem's tfifo behavior (to pfifo)
with some option. Any suggestions?

Jarek P.

  reply	other threads:[~2009-08-13 21:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1937368901.914631250159066876.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
2009-08-13 10:26 ` [Iproute2]: failed replacing internal netem qdisc with pfifo Marcela Maslanova
2009-08-13 12:03   ` Jarek Poplawski
2009-08-13 21:32     ` Jarek Poplawski [this message]
2009-08-13 21:56       ` Jarek Poplawski

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=4A848663.4020304@gmail.com \
    --to=jarkao2@gmail.com \
    --cc=kaber@trash.net \
    --cc=mmaslano@redhat.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 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).