From: "David S. Miller" <davem@redhat.com>
To: hadi@cyberus.ca
Cc: shemminger@osdl.org, util@deuroconsult.ro, netdev@oss.sgi.com,
lartc@mailman.ds9a.nl
Subject: Re: [PATCH 2.6] update to network emulation QOS scheduler
Date: Tue, 6 Jul 2004 18:51:46 -0700 [thread overview]
Message-ID: <20040706185146.4894e9d9.davem@redhat.com> (raw)
In-Reply-To: <1089164179.1039.26.camel@jzny.localdomain>
On 06 Jul 2004 21:36:20 -0400
jamal <hadi@cyberus.ca> wrote:
> Not sure what the netfilter limit target is - i suspect its something
> that limits based on a group of flows. You can still do that with a
> fwamrk at the qdisc level. Reordering needs a queue. Even the example i
> gave uses a queue that resides on the dummy device.
It's a netfilter iptables module that essentially uses sch_tbf.c's
simple token bucket filter algorithm.
See net/ipv4/netfilter/ipt_limit.c for details.
next prev parent reply other threads:[~2004-07-07 1:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 18:33 [PATCH 2.6] update to network emulation QOS scheduler Stephen Hemminger
2004-07-01 20:11 ` [PATCH 2.4] " Stephen Hemminger
2004-07-06 21:06 ` David S. Miller
2004-07-02 20:44 ` [PATCH 2.6] " Stephen Hemminger
2004-07-03 3:13 ` jamal
2004-07-06 2:49 ` David S. Miller
2004-07-06 13:04 ` jamal
2004-07-06 21:41 ` David S. Miller
2004-07-07 6:39 ` Catalin BOIE
2004-07-06 16:09 ` Stephen Hemminger
2004-07-07 1:36 ` jamal
2004-07-07 1:51 ` David S. Miller [this message]
2004-07-07 7:01 ` Catalin BOIE
2004-07-07 18:44 ` jamal
2004-07-07 18:10 ` Stephen Hemminger
2004-07-07 18:57 ` jamal
2004-07-07 20:58 ` Stephen Hemminger
2004-07-07 21:11 ` jamal
2004-07-07 21:22 ` Stephen Hemminger
2004-07-08 13:36 ` jamal
2004-07-03 13:32 ` Ed Wildgoose
2004-07-06 21:02 ` David S. Miller
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=20040706185146.4894e9d9.davem@redhat.com \
--to=davem@redhat.com \
--cc=hadi@cyberus.ca \
--cc=lartc@mailman.ds9a.nl \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
--cc=util@deuroconsult.ro \
/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).