From: Jakub Kicinski <kuba@kernel.org>
To: Felix Fietkau <nbd@nbd.name>
Cc: netdev@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net/core: add optional threading for backlog processing
Date: Mon, 27 Mar 2023 19:06:29 -0700 [thread overview]
Message-ID: <20230327190629.7e966f46@kernel.org> (raw)
In-Reply-To: <2ef8ab92-3670-61a1-384d-b827865447ca@nbd.name>
On Sat, 25 Mar 2023 06:42:43 +0100 Felix Fietkau wrote:
> >> In my tests it brings down latency (both avg and p99) considerably in
> >> some cases. I posted some numbers here:
> >> https://lore.kernel.org/netdev/e317d5bc-cc26-8b1b-ca4b-66b5328683c4@nbd.name/
> >
> > Could you provide the full configuration for this test?
> > In non-threaded mode the RPS is enabled to spread over remaining
> > 3 cores?
>
> In this test I'm using threaded NAPI and backlog_threaded without any
> fixed core assignment.
I was asking about the rps_threaded=0 side of the comparison.
So you're saying on that side you were using threaded NAPI with
no pinning and RPS across all cores?
next prev parent reply other threads:[~2023-03-28 2:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 17:13 [PATCH net-next] net/core: add optional threading for backlog processing Felix Fietkau
2023-03-24 17:20 ` Jakub Kicinski
2023-03-24 17:35 ` Felix Fietkau
2023-03-24 17:47 ` Jakub Kicinski
2023-03-24 17:57 ` Felix Fietkau
2023-03-25 3:19 ` Jakub Kicinski
2023-03-25 5:42 ` Felix Fietkau
2023-03-28 2:06 ` Jakub Kicinski [this message]
2023-03-28 9:46 ` Felix Fietkau
2023-03-28 9:29 ` Paolo Abeni
2023-03-28 9:45 ` Felix Fietkau
2023-03-28 15:13 ` Paolo Abeni
2023-03-28 15:21 ` Felix Fietkau
2023-03-29 16:14 ` Jesper Dangaard Brouer
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=20230327190629.7e966f46@kernel.org \
--to=kuba@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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.