From: Thomas Graf <tgraf@suug.ch>
To: Patrick McHardy <kaber@trash.net>
Cc: Linux Netdev List <netdev@vger.kernel.org>, jamal <hadi@cyberus.ca>
Subject: Re: [NET_SCHED]: Add mask support to fwmark classifier
Date: Fri, 25 Aug 2006 12:54:28 +0200 [thread overview]
Message-ID: <20060825105428.GR3470@postel.suug.ch> (raw)
In-Reply-To: <44EED0FC.4050108@trash.net>
* Patrick McHardy <kaber@trash.net> 2006-08-25 12:29
> This patch adds support to mask the nfmark value before the lookup
> the the fw classifier. Unfortunately it has some drawbacks, so I'd
> be interested if anyone can think of a better way.
>
> The problem is that in order to avoid walking through all filters
> contained in one instance, we need to mask the value before the
> lookup. This means all filters share the same mask, which is
> taken from the first filter created and stored in the filter head.
> The user interface however always refers to a single filter,
> not the head, so it can't be changed afterwards unless we just
> overwrite it whenever a new filter is installed. Both is not
> really perfect. The current patch doesn't allow to change the
> mark and enforces that all filters use the same one, which I think
> is better than allowing inconsistent configurations.
The other option gets down to replacing the hash table with a
list and that's not an option in my opinion. This looks very
good to me.
next prev parent reply other threads:[~2006-08-25 10:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-25 10:29 [NET_SCHED]: Add mask support to fwmark classifier Patrick McHardy
2006-08-25 10:54 ` Thomas Graf [this message]
2006-08-25 12:02 ` Patrick McHardy
2006-08-25 12:52 ` jamal
2006-08-25 14:55 ` jamal
2006-08-26 11:15 ` Patrick McHardy
-- strict thread matches above, loose matches on Subject: below --
2006-08-25 12:14 Patrick McHardy
2006-08-25 23:11 ` David 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=20060825105428.GR3470@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=hadi@cyberus.ca \
--cc=kaber@trash.net \
--cc=netdev@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 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).