From: "John A. Sullivan III" <jsullivan@opensourcedevel.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Optimizing tc filters
Date: Sat, 10 Dec 2011 16:01:46 -0500 [thread overview]
Message-ID: <1323550906.3159.183.camel@denise.theartistscloset.com> (raw)
In-Reply-To: <1323547801.4016.34.camel@edumazet-laptop>
On Sat, 2011-12-10 at 21:10 +0100, Eric Dumazet wrote:
> Le samedi 10 décembre 2011 à 14:58 -0500, John A. Sullivan III a écrit :
>
> > If we are using connection tracking in general to produce a "stateful"
> > firewall (let's just say we are - I certainly don't want to set off a
> > debate :) ), does that put #1 back on top as the most efficient since we
> > are incurring the conntrack overhead anyway or does the CONNMARK target
> > itself add considerable overhead? Thanks - John
> >
>
> CONNMARK is very cheap, no extra overhead.
>
>
OK - so I'll assume that, if using conntrac anyway, the order of
efficiency is as I outlined and, if not, #1 sinks to the bottom. If
that's not accurate, please let me know. Thanks for your help - John
prev parent reply other threads:[~2011-12-10 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-10 18:16 Optimizing tc filters John A. Sullivan III
2011-12-10 19:41 ` Eric Dumazet
2011-12-10 19:58 ` John A. Sullivan III
2011-12-10 20:10 ` Eric Dumazet
2011-12-10 21:01 ` John A. Sullivan III [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=1323550906.3159.183.camel@denise.theartistscloset.com \
--to=jsullivan@opensourcedevel.com \
--cc=eric.dumazet@gmail.com \
--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