All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] SFQ improvement ideas
Date: Mon, 14 Jan 2002 14:56:32 +0000	[thread overview]
Message-ID: <marc-lartc-101102025109116@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101094979511667@msgid-missing>

On Sun, Jan 13, 2002 at 08:21:51PM +0100, devik wrote:
> 1) Backlog depth limit

This would be nice; through proc ... but I believe it is
already being worked on by Alexey.

> 2) Interactive traffic isolation

SFQ is designed specifically to _not_ have manual isolation
of queues; use CBQ with SFQ to do this.

CBQ (all) ---- (filter interactive) --- SFQ #1
           \-- (filter everything else) --- SFQ #2

SFQ uses a hashing system to distinguish flows which is fast;
eliminating that would slow it down.  If you want simplicity
(and not CBQ), use HTB.  A classful round-robin queue would
be nice (which would do what you describe), but it would be
placed the way CBQ is above.

> 3) Hash select
> 
> Default SFQ impl. uses src(ip+port)+dst(ip+port) to distinguish
> connections. It might be useful to be able to set src(ip)+dst(ip)
> for example (do disallow users to fool SFQ by creating more connections)
> or src(ip)+dst(ip+port) to make it yet better. I'd suggest tc
> parameters like "hash " followed by set of "dip,sip,sport,dport,proto"
> arguments (e.g. ... sfq hash dip sip dport).

I agree here; it would probably be easier to just turn on or off each of
the hash criteria.

tc qdisc add dev eth0 sfq hash sip hash dip hash dport
or
tc qdisc add dev eth0 sfq hash sip hash dip
-- 
Michael T. Babcock
CTO, FibreSpeed Ltd.     (Hosting, Security, Consultation, Database, etc)
http://www.fibrespeed.net/~mbabcock/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

  parent reply	other threads:[~2002-01-14 14:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-13 19:21 [LARTC] SFQ improvement ideas devik
2002-01-13 21:06 ` John Huttley
2002-01-13 21:10 ` Daniel Wittenberg
2002-01-14  2:02 ` John Huttley
2002-01-14  4:23 ` Daniel Wittenberg
2002-01-14  5:13 ` Don Cohen
2002-01-14  9:35 ` Martin Devera
2002-01-14  9:36 ` Martin Devera
2002-01-14  9:38 ` Martin Devera
2002-01-14  9:54 ` Martin Devera
2002-01-14 14:56 ` Michael T. Babcock [this message]
2002-01-14 22:33 ` Don Cohen
2002-01-16  9:46 ` Martin Devera
2002-01-16 10:07 ` Martin Devera

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=marc-lartc-101102025109116@msgid-missing \
    --to=mbabcock@fibrespeed.net \
    --cc=lartc@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.