From: Florian Westphal <fw@strlen.de>
To: George Shuklin <george.shuklin@gmail.com>
Cc: Florian Westphal <fw@strlen.de>, Serg <seentr@at.encryp.ch>,
netfilter@vger.kernel.org
Subject: Re: Best practices on iif usage at persistent ruleset
Date: Tue, 4 Jul 2023 15:09:21 +0200 [thread overview]
Message-ID: <20230704130921.GA3751@breakpoint.cc> (raw)
In-Reply-To: <66270f9c-6465-62bd-e100-c6615df86ac2@gmail.com>
George Shuklin <george.shuklin@gmail.com> wrote:
> On 03/07/2023 18:25, Florian Westphal wrote:
> > Serg <seentr@at.encryp.ch> wrote:
> > > I know that there is iifname as a safe alternative, but as far as I know it
> > > has huge performance drawback and thus its' usage is discouraged in my case.
> > Not really. Its copy and compare 4 bytes vs. copy and compare 16 bytes.
>
> Is iface name lookup o(1)?
Yes, its just dev->name vs. dev->ifindex.
prev parent reply other threads:[~2023-07-04 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 7:40 Best practices on iif usage at persistent ruleset Serg
2023-07-03 14:04 ` George Shuklin
2023-07-03 15:25 ` Florian Westphal
2023-07-04 13:04 ` George Shuklin
2023-07-04 13:09 ` Florian Westphal [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=20230704130921.GA3751@breakpoint.cc \
--to=fw@strlen.de \
--cc=george.shuklin@gmail.com \
--cc=netfilter@vger.kernel.org \
--cc=seentr@at.encryp.ch \
/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