From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>,
netfilter-devel@vger.kernel.org, eric@garver.life
Subject: Re: [PATCH nf,v3] netfilter: nf_tables: coalesce multiple notifications into one skbuff
Date: Wed, 2 Sep 2020 18:54:42 +0200 [thread overview]
Message-ID: <20200902165442.GA19460@salvia> (raw)
In-Reply-To: <20200902163934.GF23632@orbyte.nwl.cc>
On Wed, Sep 02, 2020 at 06:39:34PM +0200, Phil Sutter wrote:
> On Wed, Sep 02, 2020 at 06:37:43PM +0200, Pablo Neira Ayuso wrote:
> > On x86_64, each notification results in one skbuff allocation which
> > consumes at least 768 bytes due to the skbuff overhead.
> >
> > This patch coalesces several notifications into one single skbuff, so
> > each notification consumes at least ~211 bytes, that ~3.5 times less
> > memory consumption. As a result, this is reducing the chances to exhaust
> > the netlink socket receive buffer.
> >
> > Rule of thumb is that each notification batch only contains netlink
> > messages whose report flag is the same, nfnetlink_send() requires this
> > to do appropriately delivery to userspace, either via unicast (echo
> > mode) or multicast (monitor mode).
> >
> > The skbuff control buffer is used to annotate the report flag for later
> > handling at the new coalescing routine.
> >
> > The batch skbuff notification size is NLMSG_GOODSIZE, using a larger
> > skbuff would allow for more socket receiver buffer savings (to amortize
> > the cost of the skbuff even more), however, going over that size might
> > break userspace applications, so let's be conservative and stick to
> > NLMSG_GOODSIZE.
> >
> > Reported-by: Phil Sutter <phil@nwl.cc>
> > Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
>
> Acked-by: Phil Sutter <phil@nwl.cc>
Thanks, I'll place this into nf.git
BTW, I assume this mitigates the problem that Eric reported? Is it
not so easy to trigger the problem after this patch?
I forgot to say, probably it would be good to monitor
/proc/net/netlink to catch how busy the socket receive buffer is
getting with your firewalld ruleset.
Thanks.
next prev parent reply other threads:[~2020-09-02 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 16:37 [PATCH nf,v3] netfilter: nf_tables: coalesce multiple notifications into one skbuff Pablo Neira Ayuso
2020-09-02 16:39 ` Phil Sutter
2020-09-02 16:54 ` Pablo Neira Ayuso [this message]
2020-09-03 8:47 ` Phil Sutter
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=20200902165442.GA19460@salvia \
--to=pablo@netfilter.org \
--cc=eric@garver.life \
--cc=netfilter-devel@vger.kernel.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).