From: "Ben Efros" <ben-ra@efros.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc filter scalability
Date: Wed, 17 Dec 2003 11:46:16 +0000 [thread overview]
Message-ID: <marc-lartc-107166524125922@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107163125829863@msgid-missing>
I no longer use the filters, instead I use the netfilter module CLASSIFY to
mark packets for certain queues....
----- Original Message -----
From: "John Hanlon - Central Coast Internet" <john@cci.net.au>
To: <lartc@mailman.ds9a.nl>
Sent: Tuesday, December 16, 2003 8:06 PM
Subject: [LARTC] tc filter scalability
> Has anyone tested the scalability of using tc filters? I have a box
> which I require to traffic shape each individual client by IP Address
using
> u32 identifiers. My concern though, is that each client requires 2 filters
> (data from and to the box) and there are a few hundred clients minimum.
> Which means each packet may have to pass through a few hundred or possibly
> thousand filters to determine its path. Is this going to give significant
> latency issues? Or excessive server load?
>
> Is there a simpler way to restrict each client to a given rate (there
> are three separate rates that different clients are assigned)?
>
> Kind regards,
>
> John Hanlon.
> Central Coast Internet.
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-12-17 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 3:20 [LARTC] tc filter scalability John Hanlon - Central Coast Internet
2003-12-17 11:46 ` Ben Efros [this message]
2003-12-17 14:14 ` Dawid Kuroczko
2003-12-19 1:01 ` John Hanlon - Central Coast Internet
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-107166524125922@msgid-missing \
--to=ben-ra@efros.com \
--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.