From: Florian Westphal <fw@strlen.de>
To: Phil Sutter <phil@nwl.cc>, Florian Westphal <fw@strlen.de>,
Pablo Neira Ayuso <pablo@netfilter.org>,
netfilter-devel@vger.kernel.org
Subject: Re: [iptables PATCH] nft: Increase BATCH_PAGE_SIZE to support huge rulesets
Date: Sat, 3 Apr 2021 13:31:59 +0200 [thread overview]
Message-ID: <20210403113159.GM13699@breakpoint.cc> (raw)
In-Reply-To: <20210403084940.GA3158@orbyte.nwl.cc>
Phil Sutter <phil@nwl.cc> wrote:
> > Isn't that library code? At the very least this should use
> > nft_print().
>
> Good point, but for the upcoming identical change to nftables! ;)
> There I'm still undecided about the best way to handle it. For iptables,
> I guess this minimal error reporting to stderr for a case that shouldn't
> happen is fine. ACK?
Oh right.
prev parent reply other threads:[~2021-04-03 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 14:53 [iptables PATCH] nft: Increase BATCH_PAGE_SIZE to support huge rulesets Phil Sutter
2021-04-02 5:38 ` Florian Westphal
2021-04-02 6:47 ` Pablo Neira Ayuso
2021-04-03 8:49 ` Phil Sutter
2021-04-03 10:23 ` Pablo Neira Ayuso
2021-04-03 11:31 ` 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=20210403113159.GM13699@breakpoint.cc \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
/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;
as well as URLs for NNTP newsgroup(s).