From: Paolo Abeni <pabeni@redhat.com>
To: Eric Dumazet <edumazet@google.com>, patchwork-bot+netdevbpf@kernel.org
Cc: netdev <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Alexander Duyck <alexanderduyck@fb.com>
Subject: Re: [PATCH net-next v4] net: skb: introduce and use a single page frag cache
Date: Fri, 30 Sep 2022 19:30:08 +0200 [thread overview]
Message-ID: <cdbfe4615ffec2bcfde94268dbc77dfa98143f39.camel@redhat.com> (raw)
In-Reply-To: <CANn89iJ=_e9-P4dvRcMzJYqpTBQ5kevEvaYFH1JVvSdv4sguhA@mail.gmail.com>
Hello,
On Fri, 2022-09-30 at 09:43 -0700, Eric Dumazet wrote:
> On Thu, Sep 29, 2022 at 7:21 PM <patchwork-bot+netdevbpf@kernel.org> wrote:
> >
> > Hello:
> >
> > This patch was applied to netdev/net-next.git (master)
> > by Jakub Kicinski <kuba@kernel.org>:
> >
> > On Wed, 28 Sep 2022 10:43:09 +0200 you wrote:
> > > After commit 3226b158e67c ("net: avoid 32 x truesize under-estimation
> > > for tiny skbs") we are observing 10-20% regressions in performance
> > > tests with small packets. The perf trace points to high pressure on
> > > the slab allocator.
> > >
> > > This change tries to improve the allocation schema for small packets
> > > using an idea originally suggested by Eric: a new per CPU page frag is
> > > introduced and used in __napi_alloc_skb to cope with small allocation
> > > requests.
> > >
> > > [...]
> >
> > Here is the summary with links:
> > - [net-next,v4] net: skb: introduce and use a single page frag cache
> > https://git.kernel.org/netdev/net-next/c/dbae2b062824
> >
>
> Paolo, this patch adds a regression for TCP RPC workloads (aka TCP_RR)
>
> Before the patch, cpus servicing NIC interrupts were allocating
> SLAB/SLUB objects for incoming packets,
> but they were also freeing skbs from TCP rtx queues when ACK packets
> were processed. SLAB/SLUB caches
> were efficient (hit ratio close to 100%)
Thank you for the report. Is that reproducible with netperf TCP_RR and
CONFIG_DEBUG_SLAB, I guess? Do I need specific request/response sizes?
Do you think a revert will be needed for 6.1?
> After the patch, these CPU only free skbs from TCP rtx queues and
> constantly have to drain their alien caches,
> thus competing with the mm spinlocks. RX skbs allocations being done
> by page frag allocation only left kfree(~1KB) calls.
>
> One way to avoid the asymmetric behavior would be to switch TCP to
> also use page frags for TX skbs,
> allocated from tcp_stream_alloc_skb()
I guess we should have:
if (<alloc size is small and NAPI_HAS_SMALL_PAGE>)
<use small page frag>
else
<use current allocator>
right in tcp_stream_alloc_skb()? or all the way down to __alloc_skb()?
Thanks!
Paolo
>
next prev parent reply other threads:[~2022-09-30 17:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 8:43 [PATCH net-next v4] net: skb: introduce and use a single page frag cache Paolo Abeni
2022-09-28 14:11 ` Eric Dumazet
2022-09-28 14:24 ` Alexander H Duyck
2022-09-30 2:21 ` patchwork-bot+netdevbpf
2022-09-30 16:43 ` Eric Dumazet
2022-09-30 17:30 ` Paolo Abeni [this message]
2022-09-30 17:45 ` Eric Dumazet
2022-10-02 14:55 ` Paolo Abeni
2022-10-03 21:40 ` Paolo Abeni
2022-10-03 22:30 ` Eric Dumazet
2022-10-05 7:33 ` Paolo Abeni
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=cdbfe4615ffec2bcfde94268dbc77dfa98143f39.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=alexanderduyck@fb.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=patchwork-bot+netdevbpf@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 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).