From: Paolo Abeni <pabeni@redhat.com>
To: Eric Dumazet <edumazet@google.com>
Cc: patchwork-bot+netdevbpf@kernel.org,
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: Wed, 05 Oct 2022 09:33:11 +0200 [thread overview]
Message-ID: <4d710ac16e549225e0802657733ce4f773e632de.camel@redhat.com> (raw)
In-Reply-To: <CANn89iKXcagXP=QkYtrsk5jFXiyvhNL=bdXJZLc5T3e3=+jSiA@mail.gmail.com>
On Mon, 2022-10-03 at 15:30 -0700, Eric Dumazet wrote:
> I was using neper ( https://github.com/google/neper ), with 100
> threads and 4000 flows.
>
> I suspect contention is hard to see unless you use a host with at
> least 128 cores.
> Also you need a lot of NIC receive queues (or use RPS to spread
> incoming packets to many cores)
Nice tool! It looks like it can load the host very easily.
I still can't observe the regression on my H/W but I see some minor
improvement with the proposed patch, FWIW.
I'll try to look for an host with more cores, but that can take a lot
to unlimited time.
>
Cheers,
Paolo
prev parent reply other threads:[~2022-10-05 7:33 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
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 [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=4d710ac16e549225e0802657733ce4f773e632de.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).