From: Jakub Kicinski <kuba@kernel•org>
To: Tariq Toukan <ttoukan.linux@gmail•com>
Cc: davem@davemloft•net, netdev@vger•kernel.org, edumazet@google•com,
pabeni@redhat•com, hawk@kernel•org, ilias.apalodimas@linaro•org,
linyunsheng@huawei•com, Dragos Tatulea <dtatulea@nvidia•com>
Subject: Re: [PATCH net-next 0/3] page_pool: allow caching from safely localized NAPI
Date: Wed, 12 Apr 2023 21:18:14 -0700 [thread overview]
Message-ID: <20230412211814.273fd0a5@kernel.org> (raw)
In-Reply-To: <c433e59d-1262-656e-b08c-30adfc12edcc@gmail.com>
On Wed, 12 Apr 2023 09:41:16 +0300 Tariq Toukan wrote:
> Happy holidays! I was traveling and couldn't review the RFCs.
>
> Dragos and I had this task in our plans after our recent page pool work
> in mlx5e. We're so glad to see this patchset! :)
I may end up sending some hacks for mlx4 depending on what results I get,
I wonder if the reaction will be as enthusiastic :)
prev parent reply other threads:[~2023-04-13 4:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 20:17 [PATCH net-next 0/3] page_pool: allow caching from safely localized NAPI Jakub Kicinski
2023-04-11 20:17 ` [PATCH net-next 1/3] net: skb: plumb napi state thru skb freeing paths Jakub Kicinski
2023-04-12 9:29 ` Jesper Dangaard Brouer
2023-04-13 4:20 ` Jakub Kicinski
2023-04-11 20:17 ` [PATCH net-next 2/3] page_pool: allow caching from safely localized NAPI Jakub Kicinski
2023-04-11 20:18 ` [PATCH net-next 3/3] bnxt: hook NAPIs to page pools Jakub Kicinski
2023-04-12 6:41 ` [PATCH net-next 0/3] page_pool: allow caching from safely localized NAPI Tariq Toukan
2023-04-12 6:56 ` Tariq Toukan
2023-04-13 4:18 ` 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=20230412211814.273fd0a5@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dtatulea@nvidia$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=hawk@kernel$(echo .)org \
--cc=ilias.apalodimas@linaro$(echo .)org \
--cc=linyunsheng@huawei$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=ttoukan.linux@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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