From: Jakub Kicinski <kuba@kernel.org>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, Bagas Sanjaya <bagasdotme@gmail.com>,
Toke HHHiland-JJJrgensen <toke@redhat.com>,
corbet@lwn.net, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, pisa@cmp.felk.cvut.cz,
mkl@pengutronix.de, linux-doc@vger.kernel.org,
f.fainelli@gmail.com, stephen@networkplumber.org
Subject: Re: [PATCH net-next v2] docs: networking: document NAPI
Date: Tue, 21 Mar 2023 17:50:19 -0700 [thread overview]
Message-ID: <20230321175019.3b6a525a@kernel.org> (raw)
In-Reply-To: <20230322001338.GA452632@electric-eye.fr.zoreil.com>
On Wed, 22 Mar 2023 01:13:38 +0100 Francois Romieu wrote:
> NAPI processing also happens in the unusual context of netpoll.
>
> I can't tell if it's better to be completely silent about it or to
> explicitely state that it is beyond the scope of the document.
I stayed away from it, because from the perspective of driver
developers and users the calling contexts should not be depended on.
So I tried to stay vague on that, and explain what they should do
rather than what the core does.
prev parent reply other threads:[~2023-03-22 0:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 5:03 [PATCH net-next v2] docs: networking: document NAPI Jakub Kicinski
2023-03-21 13:14 ` Pavel Pisa
2023-03-21 17:05 ` Stephen Hemminger
2023-03-22 0:44 ` Jakub Kicinski
2023-03-21 17:18 ` Tony Nguyen
2023-03-22 0:46 ` Jakub Kicinski
2023-03-21 20:50 ` Florian Fainelli
2023-03-22 0:13 ` Francois Romieu
2023-03-22 0:50 ` Jakub Kicinski [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=20230321175019.3b6a525a@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=jesse.brandeburg@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pisa@cmp.felk.cvut.cz \
--cc=romieu@fr.zoreil.com \
--cc=stephen@networkplumber.org \
--cc=toke@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 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).