From: Larysa Zaremba <larysa.zaremba@intel.com>
To: Gal Pressman <gal@nvidia.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next 0/2] Couple of minor improvements to build_skb variants
Date: Wed, 15 Feb 2023 16:03:59 +0100 [thread overview]
Message-ID: <Y+z0Xxrj6HXl7djG@lincoln> (raw)
In-Reply-To: <20230215121707.1936762-1-gal@nvidia.com>
On Wed, Feb 15, 2023 at 02:17:05PM +0200, Gal Pressman wrote:
> First patch replaces open-coded occurrences of
> skb_propagate_pfmemalloc() in build_skb() and build_skb_around().
> The secnod patch adds a likely() to the skb allocation in build_skb().
>
> Thanks
>
> Gal Pressman (2):
> skbuff: Replace open-coded skb_propagate_pfmemalloc()s
> skbuff: Add likely to skb pointer in build_skb()
>
> net/core/skbuff.c | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
Reviewed-by: Larysa Zaremba <larysa.zaremba@intel.com>
> --
> 2.39.0
>
prev parent reply other threads:[~2023-02-15 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 12:17 [PATCH net-next 0/2] Couple of minor improvements to build_skb variants Gal Pressman
2023-02-15 12:17 ` [PATCH net-next 1/2] skbuff: Replace open-coded skb_propagate_pfmemalloc()s Gal Pressman
2023-02-15 12:17 ` [PATCH net-next 2/2] skbuff: Add likely to skb pointer in build_skb() Gal Pressman
2023-02-15 23:01 ` Jakub Kicinski
2023-02-16 14:55 ` Gal Pressman
2023-02-16 15:00 ` Paolo Abeni
2023-02-16 12:15 ` Paolo Abeni
2023-02-15 15:03 ` Larysa Zaremba [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=Y+z0Xxrj6HXl7djG@lincoln \
--to=larysa.zaremba@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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