From: "Samudrala, Sridhar" <sridhar.samudrala@intel.com>
To: Joe Damato <jdamato@fastly.com>, <netdev@vger.kernel.org>
Cc: <bagasdotme@gmail.com>, <pabeni@redhat.com>,
<namangulati@google.com>, <edumazet@google.com>,
<amritha.nambiar@intel.com>, <sdf@fomichev.me>,
<peter@typeblog.net>, <m2shafiei@uwaterloo.ca>,
<bjorn@rivosinc.com>, <hch@infradead.org>, <willy@infradead.org>,
<willemdebruijn.kernel@gmail.com>, <skhawaja@google.com>,
<kuba@kernel.org>, Martin Karsten <mkarsten@uwaterloo.ca>,
Donald Hunter <donald.hunter@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Simon Horman" <horms@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"Jesper Dangaard Brouer" <hawk@kernel.org>,
Mina Almasry <almasrymina@google.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
David Ahern <dsahern@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Alexander Lobakin <aleksander.lobakin@intel.com>,
"Jiri Pirko" <jiri@resnulli.us>,
Johannes Berg <johannes.berg@intel.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v4 1/7] net: Add napi_struct parameter irq_suspend_timeout
Date: Sat, 2 Nov 2024 18:30:47 -0500 [thread overview]
Message-ID: <a7bddab1-ae24-4e38-97b0-9f7467084c15@intel.com> (raw)
In-Reply-To: <20241102005214.32443-2-jdamato@fastly.com>
On 11/1/2024 7:51 PM, Joe Damato wrote:
> From: Martin Karsten <mkarsten@uwaterloo.ca>
>
> Add a per-NAPI IRQ suspension parameter, which can be get/set with
> netdev-genl.
>
> This patch doesn't change any behavior but prepares the code for other
> changes in the following commits which use irq_suspend_timeout as a
> timeout for IRQ suspension.
>
> Signed-off-by: Martin Karsten <mkarsten@uwaterloo.ca>
> Co-developed-by: Joe Damato <jdamato@fastly.com>
> Signed-off-by: Joe Damato <jdamato@fastly.com>
> Tested-by: Joe Damato <jdamato@fastly.com>
> Tested-by: Martin Karsten <mkarsten@uwaterloo.ca>
> Acked-by: Stanislav Fomichev <sdf@fomichev.me>
> ---
Reviewed-by: Sridhar Samudrala <sridhar.samudrala@intel.com>
next prev parent reply other threads:[~2024-11-02 23:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-02 0:51 [PATCH net-next v4 0/7] Suspend IRQs during application busy periods Joe Damato
2024-11-02 0:51 ` [PATCH net-next v4 1/7] net: Add napi_struct parameter irq_suspend_timeout Joe Damato
2024-11-02 23:30 ` Samudrala, Sridhar [this message]
2024-11-02 0:51 ` [PATCH net-next v4 2/7] net: Suspend softirq when prefer_busy_poll is set Joe Damato
2024-11-02 23:32 ` Samudrala, Sridhar
2024-11-02 0:51 ` [PATCH net-next v4 3/7] net: Add control functions for irq suspension Joe Damato
2024-11-02 23:33 ` Samudrala, Sridhar
2024-11-02 0:52 ` [PATCH net-next v4 4/7] eventpoll: Trigger napi_busy_loop, if prefer_busy_poll is set Joe Damato
2024-11-02 23:33 ` Samudrala, Sridhar
2024-11-02 0:52 ` [PATCH net-next v4 5/7] eventpoll: Control irq suspension for prefer_busy_poll Joe Damato
2024-11-02 23:35 ` Samudrala, Sridhar
2024-11-02 23:39 ` Hillf Danton
2024-11-03 4:10 ` Joe Damato
2024-11-02 0:52 ` [PATCH net-next v4 6/7] selftests: net: Add busy_poll_test Joe Damato
2024-11-02 0:52 ` [PATCH net-next v4 7/7] docs: networking: Describe irq suspension Joe Damato
2024-11-02 23:41 ` Samudrala, Sridhar
2024-11-02 23:51 ` [PATCH net-next v4 0/7] Suspend IRQs during application busy periods Hillf Danton
2024-11-03 1:50 ` Joe Damato
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=a7bddab1-ae24-4e38-97b0-9f7467084c15@intel.com \
--to=sridhar.samudrala@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=almasrymina@google.com \
--cc=amritha.nambiar@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=bagasdotme@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=bjorn@rivosinc.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=hch@infradead.org \
--cc=horms@kernel.org \
--cc=jdamato@fastly.com \
--cc=jiri@resnulli.us \
--cc=johannes.berg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=m2shafiei@uwaterloo.ca \
--cc=mkarsten@uwaterloo.ca \
--cc=namangulati@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peter@typeblog.net \
--cc=sdf@fomichev.me \
--cc=skhawaja@google.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=willy@infradead.org \
--cc=xuanzhuo@linux.alibaba.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