From: Patrick McHardy <kaber@trash.net>
To: Thomas Graf <tgraf@suug.ch>
Cc: Asim Shankar <asimshankar@gmail.com>, netdev@oss.sgi.com
Subject: Re: SFQ: Reordering?
Date: Sat, 07 May 2005 01:19:14 +0200 [thread overview]
Message-ID: <427BFB72.7080407@trash.net> (raw)
In-Reply-To: <20050506230203.GI28419@postel.suug.ch>
Thomas Graf wrote:
> We can maintain a second hash table and switch a pointer over to the
> new table but keep on dequeueing from the old one until it is empty.
> Anyways, any such behaviour should be made optional via a rtnetlink
> flag.
This also introduces unfairness. Packets of a flow could be only in
the new table while we're still working on the active table.
A proper solution to avoid reordering shouldn't be optional IMO,
perturbation is already optional.
Regards
Patrick
next prev parent reply other threads:[~2005-05-06 23:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 21:53 SFQ: Reordering? Asim Shankar
2005-05-06 22:07 ` Patrick McHardy
2005-05-06 22:46 ` Patrick McHardy
2005-05-06 23:02 ` Thomas Graf
2005-05-06 23:19 ` Patrick McHardy [this message]
2005-05-07 0:58 ` Thomas Graf
2005-05-07 1:28 ` Patrick McHardy
2005-05-08 11:51 ` Thomas Graf
2005-05-08 16:03 ` Patrick McHardy
2005-05-08 18:33 ` Thomas Graf
2005-05-09 23:14 ` Andy Furniss
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=427BFB72.7080407@trash.net \
--to=kaber@trash.net \
--cc=asimshankar@gmail.com \
--cc=netdev@oss.sgi.com \
--cc=tgraf@suug.ch \
/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).