From: David Boreham <david_list@boreham.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] FW: Some queueing disciplines that I wrote.
Date: Sun, 16 Oct 2005 17:22:15 +0000 [thread overview]
Message-ID: <43528C47.9040301@boreham.org> (raw)
In-Reply-To: <9A21B9DC026C80439FBD8C5B197AE04B70CD91@zeta.usq.edu.au>
Stephen Braithwaite wrote:
>The definition of a flow need not be the TCP definition of a flow.
>I am not sure if it will help, but any the queuing discipline and ingress que filter are
>able to work with any combination of protocol, source port number, source ip, dest port, dest ip as the definition of a flow. This may or may not help.
>
>
Ah, that's very interesting. So you could assign all traffic to/from a
'hog' ISP customer to the elephant category.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-10-16 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 14:05 [LARTC] FW: Some queueing disciplines that I wrote Stephen Braithwaite
2005-10-15 14:14 ` David Boreham
2005-10-15 14:28 ` Stephen Braithwaite
2005-10-15 19:35 ` panca sorin
2005-10-16 2:42 ` Stephen Braithwaite
2005-10-16 17:22 ` David Boreham [this message]
2005-10-17 0:30 ` Stephen Braithwaite
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=43528C47.9040301@boreham.org \
--to=david_list@boreham.org \
--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.