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:56:00 +0200 [thread overview]
Message-ID: <4A848BF0.1030505@gmail.com> (raw)
In-Reply-To: <4A848663.4020304@gmail.com>
Jarek Poplawski wrote, On 08/13/2009 11:32 PM:
...
> 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?
...or something in between like classfulness limited to fifos only?
Jarek P.
prev parent reply other threads:[~2009-08-13 21:56 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
2009-08-13 21:56 ` Jarek Poplawski [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=4A848BF0.1030505@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).