From: Jakub Kicinski <kuba@kernel.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jesper Dangaard Brouer <hawk@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Wander Lairson Costa <wander@redhat.com>,
Yan Zhai <yan@cloudflare.com>
Subject: Re: [PATCH v2 net-next 3/3] net: Use backlog-NAPI to clean up the defer_list.
Date: Mon, 26 Feb 2024 17:22:33 -0800 [thread overview]
Message-ID: <20240226172233.161c6e7e@kernel.org> (raw)
In-Reply-To: <20240226115922.3ghr5wuD@linutronix.de>
On Mon, 26 Feb 2024 12:59:22 +0100 Sebastian Andrzej Siewior wrote:
> They protect the list in input_pkt_queue and the NAPI state. It is just
> in the !RPS case it is always CPU-local and the lock is avoided (while
> interrupts are still disabled/ enabled).
>
> What about
> input_queue_lock_irq_save()
> input_queue_lock_irq_disable()
> input_queue_lock_irq_restore()
> input_queue_lock_irq_enable()
SGTM. Maybe I'd risk calling it backlog_lock_* but not sure others
would agree.
next prev parent reply other threads:[~2024-02-27 1:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 17:00 [PATCH v2 net-next 0/3] net: Provide SMP threads for backlog NAPI Sebastian Andrzej Siewior
2024-02-21 17:00 ` [PATCH v2 net-next 1/3] net: Remove conditional threaded-NAPI wakeup based on task state Sebastian Andrzej Siewior
2024-02-21 17:00 ` [PATCH v2 net-next 2/3] net: Allow to use SMP threads for backlog NAPI Sebastian Andrzej Siewior
2024-02-21 17:00 ` [PATCH v2 net-next 3/3] net: Use backlog-NAPI to clean up the defer_list Sebastian Andrzej Siewior
2024-02-24 2:02 ` Jakub Kicinski
2024-02-26 11:59 ` Sebastian Andrzej Siewior
2024-02-27 1:22 ` Jakub Kicinski [this message]
2024-02-27 7:27 ` Sebastian Andrzej Siewior
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=20240226172233.161c6e7e@kernel.org \
--to=kuba@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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 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).