From: Pablo Neira Ayuso <pablo@netfilter.org>
To: alexandre.ferrieux@orange.com
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: nfnetlink_queue -- why linear lookup ?
Date: Sun, 15 Aug 2021 15:07:16 +0200 [thread overview]
Message-ID: <20210815130716.GA21655@salvia> (raw)
In-Reply-To: <27263_1629029795_611905A3_27263_246_1_ddbb7a24-d843-9985-5833-c7c8c1aa8d29@orange.com>
On Sun, Aug 15, 2021 at 02:17:08PM +0200, alexandre.ferrieux@orange.com wrote:
[...]
> So, the only way forward would be a separate hashtable on ids.
Using the rhashtable implementation is fine for this, it's mostly
boilerplate code that is needed to use it and there are plenty of
examples in the kernel tree if you need a reference.
[...]
> PS: what is the intended dominant use case for batch verdicts ?
Issuing a batch containing several packets helps to amortize the
cost of the syscall.
next prev parent reply other threads:[~2021-08-15 13:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 11:55 nfnetlink_queue -- why linear lookup ? alexandre.ferrieux
2021-08-14 21:01 ` Florian Westphal
2021-08-14 21:05 ` alexandre.ferrieux
2021-08-14 21:12 ` Florian Westphal
2021-08-15 12:17 ` alexandre.ferrieux
2021-08-15 13:07 ` Pablo Neira Ayuso [this message]
2021-08-15 13:32 ` alexandre.ferrieux
2021-08-15 14:12 ` Pablo Neira Ayuso
2021-08-15 18:47 ` alexandre.ferrieux
2021-08-16 9:05 ` Pablo Neira Ayuso
2021-08-16 10:53 ` alexandre.ferrieux
2021-08-16 10:56 ` Florian Westphal
2021-08-16 11:07 ` alexandre.ferrieux
2021-08-16 11:19 ` Pablo Neira Ayuso
2021-08-16 11:42 ` Duncan Roe
2021-08-16 12:04 ` Duncan Roe
2021-08-16 16:10 ` Pablo Neira Ayuso
2021-08-16 16:15 ` Florian Westphal
2021-08-17 4:03 ` Duncan Roe
2021-08-15 13:33 ` alexandre.ferrieux
-- strict thread matches above, loose matches on Subject: below --
2021-08-13 11:10 alexandre.ferrieux
2021-08-13 10:58 alexandre.ferrieux
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=20210815130716.GA21655@salvia \
--to=pablo@netfilter.org \
--cc=alexandre.ferrieux@orange.com \
--cc=fw@strlen.de \
--cc=netfilter-devel@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.