From: Jakub Kicinski <kuba@kernel.org>
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, "Bagas Sanjaya" <bagasdotme@gmail.com>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
"Pavel Pisa" <pisa@cmp.felk.cvut.cz>,
"Tony Nguyen" <anthony.l.nguyen@intel.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
corbet@lwn.net, jesse.brandeburg@intel.com, mkl@pengutronix.de,
linux-doc@vger.kernel.org, stephen@networkplumber.org,
romieu@fr.zoreil.com
Subject: Re: [PATCH net-next v3] docs: networking: document NAPI
Date: Thu, 23 Mar 2023 19:42:35 -0700 [thread overview]
Message-ID: <20230323194235.66fbd368@kernel.org> (raw)
In-Reply-To: <e9caa256-482d-1cc0-4244-e9d4c5615f01@blackwall.org>
On Wed, 22 Mar 2023 12:39:59 +0200 Nikolay Aleksandrov wrote:
> > +It is recommended to pin each kernel thread to a single CPU, the same
> > +CPU as services the interrupt. Note that the mapping between IRQs and
>
> "... the same CPU as services the interrupt ...", should it be
> "the same CPU that services the interrupt" ?
"the same as" is a very common idiom.
There's a slight ellipsis there, perhaps, the full sentence is:
| It is recommended to pin each kernel thread to a single CPU, the same
| CPU as [the CPU which] services the interrupt.
Let me add the missing part.
next prev parent reply other threads:[~2023-03-24 2:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 5:38 [PATCH net-next v3] docs: networking: document NAPI Jakub Kicinski
2023-03-22 10:39 ` Nikolay Aleksandrov
2023-03-24 2:42 ` Jakub Kicinski [this message]
2023-03-22 15:05 ` Stephen Hemminger
2023-03-22 18:47 ` Randy Dunlap
2023-03-22 23:21 ` Jakub Kicinski
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=20230323194235.66fbd368@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=razor@blackwall.org \
--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).