From: Jacob Keller <jacob.e.keller@intel.com>
To: Mina Almasry <almasrymina@google.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Ayush Sawal <ayush.sawal@chelsio.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jesper Dangaard Brouer <hawk@kernel.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
"Steffen Klassert" <steffen.klassert@secunet.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
David Ahern <dsahern@kernel.org>,
"Boris Pismenny" <borisp@nvidia.com>,
John Fastabend <john.fastabend@gmail.com>,
Dragos Tatulea <dtatulea@nvidia.com>
Subject: Re: [PATCH net-next v5 3/3] net: remove napi_frag_unref
Date: Tue, 9 Apr 2024 16:58:52 -0700 [thread overview]
Message-ID: <c4976cb1-ef18-42f5-acbe-0c053bc4b141@intel.com> (raw)
In-Reply-To: <20240408153000.2152844-4-almasrymina@google.com>
On 4/8/2024 8:29 AM, Mina Almasry wrote:
> With the changes in the last patches, napi_frag_unref() is now
> reduandant. Remove it and use skb_page_unref directly.
>
> Signed-off-by: Mina Almasry <almasrymina@google.com>
> Reviewed-by: Dragos Tatulea <dtatulea@nvidia.com>
> Reviewed-by: Eric Dumazet <edumazet@google.com>
>
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
next prev parent reply other threads:[~2024-04-09 23:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 15:29 [PATCH net-next v5 0/3] Minor cleanups to skb frag ref/unref Mina Almasry
2024-04-08 15:29 ` [PATCH net-next v5 1/3] net: make napi_frag_unref reuse skb_page_unref Mina Almasry
2024-04-09 23:56 ` Jacob Keller
2024-04-08 15:29 ` [PATCH net-next v5 2/3] net: mirror skb frag ref/unref helpers Mina Almasry
2024-04-09 23:58 ` Jacob Keller
2024-04-10 1:23 ` Jakub Kicinski
2024-04-10 19:09 ` Mina Almasry
2024-04-08 15:29 ` [PATCH net-next v5 3/3] net: remove napi_frag_unref Mina Almasry
2024-04-09 23:58 ` Jacob Keller [this message]
2024-04-10 1:50 ` [PATCH net-next v5 0/3] Minor cleanups to skb frag ref/unref patchwork-bot+netdevbpf
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=c4976cb1-ef18-42f5-acbe-0c053bc4b141@intel.com \
--to=jacob.e.keller@intel.com \
--cc=almasrymina@google.com \
--cc=ayush.sawal@chelsio.com \
--cc=borisp@nvidia.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=ilias.apalodimas@linaro.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.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
Powered by JetHome