From: Florian Westphal <fw@strlen.de>
To: Jozsef Kadlecsik <kadlec@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf v6 0/6] ipset: replace internal hash table with rhashtable
Date: Tue, 27 Oct 2026 19:04:45 +0100 [thread overview]
Message-ID: <auDnvef-koFIKKft@strlen.de> (raw)
In-Reply-To: <a8a94db7-7b61-4619-e7d9-920e775814b7@netfilter.org>
Jozsef Kadlecsik <kadlec@netfilter.org> wrote:
> Hi Florian,
>
> I'm absolutely sure that your efforts to replace the custom hash
> implementation in ipset with rhastable is the proper way to solve the many
> problems lurking in the current codebase. Which are sometimes nearly
> impossible to solve anyway, without a complete redesign. So looking at the
> sashiko comments, I think the end of the long journey is not far away!
Its farther away than ever. Totally demotivating.
Each new iteration moves goalpost and raises new concerns not seen
before, or raised by other models.
I hope I can retire within the next few years, the AI age sucked all the
fun out of it.
prev parent reply other threads:[~2026-10-27 18:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 13:33 [PATCH nf v6 0/6] ipset: replace internal hash table with rhashtable Florian Westphal
2026-10-27 13:33 ` [PATCH nf v6 1/6] rhashtable: Add rhashtable_flush_and_free helper Florian Westphal
2026-10-27 13:33 ` [PATCH nf v6 2/6] netfilter: ipset: add rhashtable boilerplate stubs Florian Westphal
2026-10-27 13:33 ` [PATCH nf v6 3/6] netfilter: ipset: add rhltable " Florian Westphal
2026-10-27 13:33 ` [PATCH nf v6 4/6] netfilter: ipset: replace internal hash table with rhashtable Florian Westphal
2026-10-27 13:33 ` [PATCH nf v6 5/6] netfilter: ipset: re-add forceadd support Florian Westphal
2026-10-27 13:33 ` [PATCH nf v6 6/6] netfilter: ipset: also report mem size for cidr storage to userspace Florian Westphal
2026-10-27 17:13 ` [PATCH nf v6 0/6] ipset: replace internal hash table with rhashtable Jozsef Kadlecsik
2026-10-27 18:04 ` 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=auDnvef-koFIKKft@strlen.de \
--to=fw@strlen.de \
--cc=kadlec@netfilter.org \
--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.