From: Jakub Kicinski <kuba@kernel.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Yan Zhai <yan@cloudflare.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Wander Lairson Costa <wander@redhat.com>,
Jesper Dangaard Brouer <hawk@kernel.org>
Subject: Re: [RFC PATCH net-next 0/2] net: Use SMP threads for backlog NAPI.
Date: Fri, 18 Aug 2023 09:21:11 -0700 [thread overview]
Message-ID: <20230818092111.5d86e351@kernel.org> (raw)
In-Reply-To: <20230818145734.OgLYhPh1@linutronix.de>
On Fri, 18 Aug 2023 16:57:34 +0200 Sebastian Andrzej Siewior wrote:
> As of now Jakub isn't eager to have it and my testing/ convincing is
> quite limited. If nobody else yells that something like that would be
> helpful I would simply go and convince PeterZ/tglx to apply 2/2 of this
> series.
As tempting as code removal would be, we can still try to explore the
option of letting backlog processing run in threads - as an opt-in on
normal kernels and force it on RT?
But it would be good to wait ~2 weeks before moving forward, if you
don't mind, various core folks keep taking vacations..
next prev parent reply other threads:[~2023-08-18 16:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 9:35 [RFC PATCH net-next 0/2] net: Use SMP threads for backlog NAPI Sebastian Andrzej Siewior
2023-08-14 9:35 ` [RFC PATCH net-next 1/2] " Sebastian Andrzej Siewior
2023-08-21 8:32 ` kernel test robot
2023-08-23 13:35 ` Paolo Abeni
2023-09-20 15:57 ` Sebastian Andrzej Siewior
2023-09-21 10:41 ` Ferenc Fejes
2023-09-22 7:26 ` Sebastian Andrzej Siewior
2023-09-22 9:38 ` Paolo Abeni
2023-08-14 9:35 ` [RFC PATCH 2/2] softirq: Drop the warning from do_softirq_post_smp_call_flush() Sebastian Andrzej Siewior
2023-08-15 12:08 ` Jesper Dangaard Brouer
2023-08-15 22:31 ` Yan Zhai
2023-08-16 14:48 ` Jesper Dangaard Brouer
2023-08-16 15:15 ` Yan Zhai
2023-08-16 21:02 ` Jesper Dangaard Brouer
2023-08-18 15:49 ` Yan Zhai
2023-08-16 15:22 ` Sebastian Andrzej Siewior
2023-08-14 18:24 ` [RFC PATCH net-next 0/2] net: Use SMP threads for backlog NAPI Jakub Kicinski
2023-08-17 13:16 ` Sebastian Andrzej Siewior
2023-08-17 15:30 ` Jakub Kicinski
2023-08-18 9:03 ` Sebastian Andrzej Siewior
2023-08-18 14:43 ` Yan Zhai
2023-08-18 14:57 ` Sebastian Andrzej Siewior
2023-08-18 16:21 ` Jakub Kicinski [this message]
2023-08-18 16:40 ` Eric Dumazet
2023-08-23 6:57 ` Sebastian Andrzej Siewior
2023-08-18 16:56 ` Yan Zhai
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=20230818092111.5d86e351@kernel.org \
--to=kuba@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=wander@redhat.com \
--cc=yan@cloudflare.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.