From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: Current Script
Date: Wed, 15 Jun 2005 10:59:50 +0000 [thread overview]
Message-ID: <42B00A26.5080007@dsl.pipex.com> (raw)
In-Reply-To: <42AF7C6A.90100@dsl.pipex.com>
Andy Furniss wrote:
> I think the way you are using classify means that each packet has to go
> through 4x more checks than if you did the same thing with --or-mark but
> with 53 users it may not be worth the extra hassle of optimising.
Although you could get the same reduction using classify in combination
with a user defined chain for each class of traffic.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-06-15 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 0:55 [LARTC] Re: Current Script Andy Furniss
2005-06-15 10:59 ` Andy Furniss [this message]
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=42B00A26.5080007@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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.