netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Graf <tgraf@suug.ch>
To: Patrick McHardy <kaber@trash.net>
Cc: Asim Shankar <asimshankar@gmail.com>, netdev@oss.sgi.com
Subject: Re: SFQ: Reordering?
Date: Sat, 7 May 2005 02:58:51 +0200	[thread overview]
Message-ID: <20050507005851.GK28419@postel.suug.ch> (raw)
In-Reply-To: <427BFB72.7080407@trash.net>

* Patrick McHardy <427BFB72.7080407@trash.net> 2005-05-07 01:19
> 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.

Yes, that's true but we can't reach perfect fairness anyway. What
is your primary goal? No reordering inside flows while staying
as fair as possible? I'm not sure whether it's worth to rehash
every single enqueued packet, especially not at a perturbation
interval of just a few seconds. Many scripts set it to a value
of 1..5 to have a higher theoreticaly fairness. That's why I think
this feature should be made optional

  reply	other threads:[~2005-05-07  0:58 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
2005-05-07  0:58         ` Thomas Graf [this message]
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=20050507005851.GK28419@postel.suug.ch \
    --to=tgraf@suug.ch \
    --cc=asimshankar@gmail.com \
    --cc=kaber@trash.net \
    --cc=netdev@oss.sgi.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).