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: Sun, 8 May 2005 13:51:00 +0200	[thread overview]
Message-ID: <20050508115100.GQ28419@postel.suug.ch> (raw)
In-Reply-To: <427C19C3.5030304@trash.net>

* Patrick McHardy <427C19C3.5030304@trash.net> 2005-05-07 03:28
> You stated my goal precisely :) I know many people set the interval
> to too low values, but because of the tight limits, it shouldn't be
> very expensive anyways. Table switching OTOH would introduce frequently
> occuring unfairness, and the time to work through a full table is
> a lot longer, especially in the environments where SFQ is used.

I think you are right on this so forget about my thought. Maybe as
an additional input it might be worth mentioning that I have patches
ready to a) make the sfq depth adjustable and b) hash algorithm
selection to a few builtin ones and additional to read theh hash
from tc_classid set by an action. A real world example where this
is useful is for routers primarly doing SNAT without any own local
traffic where hashing algorithm primarly based on the source port
makes a lot more sense.

  reply	other threads:[~2005-05-08 11:51 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
2005-05-07  1:28           ` Patrick McHardy
2005-05-08 11:51             ` Thomas Graf [this message]
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=20050508115100.GQ28419@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).