From: Florian Westphal <fw@strlen.de>
To: alexandre.ferrieux@orange.com
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Florian Westphal <fw@strlen.de>,
netfilter-devel@vger.kernel.org
Subject: Re: nfnetlink_queue -- why linear lookup ?
Date: Mon, 16 Aug 2021 12:56:41 +0200 [thread overview]
Message-ID: <20210816105641.GM607@breakpoint.cc> (raw)
In-Reply-To: <19560_1629111179_611A438B_19560_274_1_0633ee7a-2660-91b4-f1d7-adc727864376@orange.com>
alexandre.ferrieux@orange.com <alexandre.ferrieux@orange.com> wrote:
> Well, the problem is backwards compatibility. Indeed I'd propose more
> flexible batching via an array of ids instead of a maxid. But the main added
> value of this flexibility is to enable reused-small-integers ids, like file
> descriptors. As long as the maxid API remains in place, this is impossible.
You cannot remove the maxid API.
next prev parent reply other threads:[~2021-08-16 10:56 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
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 [this message]
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=20210816105641.GM607@breakpoint.cc \
--to=fw@strlen.de \
--cc=alexandre.ferrieux@orange.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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.