From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: "Mike Rapoport (Microsoft)" <rppt@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
"Manish Chopra" <manishc@marvell.com>,
Paolo Abeni <pabeni@redhat.com>
Cc: Edward Cree <ecree.xilinx@gmail.com>,
Sudarsana Kalluru <skalluru@marvell.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
<intel-wired-lan@lists.osuosl.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<linux-net-drivers@amd.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH 2/4] ice: use kzalloc() to allocate staging buffer for reading from GNSS
Date: Thu, 2 Jul 2026 15:49:36 +0200 [thread overview]
Message-ID: <d2c75404-a87f-4bb6-b17c-c921d08a1f15@intel.com> (raw)
In-Reply-To: <20260701-b4-drivers-ethernet-v1-2-58776615db6e@kernel.org>
On 7/1/26 15:57, Mike Rapoport (Microsoft) wrote:
> ice_gnss_read() uses get_zeroed_page() to allocate a staging buffer for
> reading GNSS module data via I2C bus.
>
> This buffer can be allocated with kmalloc() as there's nothing special
> about it to go directly to the page allocator.
>
> kmalloc() provides a better API that does not require ugly casts and
> kfree() does not need to know the size of the freed object.
>
> Performance difference between kmalloc() and __get_free_pages() is not
> measurable as both allocators take an object/page from a per-CPU list for
> fast path allocations.
>
> For the slow path the performance is anyway determined by the amount of
> reclaim involved rather than by what allocator is used.
>
> Replace use of get_zeroed_page() with kzalloc() and free_page() with
> kfree().
>
> Link: https://lore.kernel.org/all/635405e4-9423-4a25-a6e7-e03c8ea0bcbe@redhat.com
> Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
> drivers/net/ethernet/intel/ice/ice_gnss.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/ice/ice_gnss.c b/drivers/net/ethernet/intel/ice/ice_gnss.c
> index 8fd954f1ebd6..7d21c3417b0b 100644
> --- a/drivers/net/ethernet/intel/ice/ice_gnss.c
> +++ b/drivers/net/ethernet/intel/ice/ice_gnss.c
> @@ -2,6 +2,7 @@
> /* Copyright (C) 2021-2022, Intel Corporation. */
>
> #include "ice.h"
> +#include <linux/slab.h>
> #include "ice_lib.h"
>
> /**
> @@ -124,7 +125,7 @@ static void ice_gnss_read(struct kthread_work *work)
>
> data_len = min_t(typeof(data_len), data_len, PAGE_SIZE);
>
> - buf = (char *)get_zeroed_page(GFP_KERNEL);
> + buf = kzalloc(PAGE_SIZE, GFP_KERNEL);
nit:
from the code it is clear that we read at most a page, and @data_len
stores the actual amount needed
comment:
I don't know why we limit to a page, it's outside of the scope of this
series, but likely you have removed the limit (which will go into the
loop - single AQ call is likely limited by a PAGE too).
Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> if (!buf) {
> err = -ENOMEM;
> goto requeue;
> @@ -151,7 +152,7 @@ static void ice_gnss_read(struct kthread_work *work)
> count, i);
> delay = ICE_GNSS_TIMER_DELAY_TIME;
> free_buf:
> - free_page((unsigned long)buf);
> + kfree(buf);
> requeue:
> kthread_queue_delayed_work(gnss->kworker, &gnss->read_work, delay);
> if (err)
>
next prev parent reply other threads:[~2026-07-02 13:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 13:57 [PATCH 0/4] drivers/net/ethernet: replace __get_free_pages() with kmalloc() Mike Rapoport (Microsoft)
2026-07-01 13:57 ` [PATCH 1/4] bnx2x: use kzalloc() to allocate mac filtering list Mike Rapoport (Microsoft)
2026-07-02 13:52 ` Przemek Kitszel
2026-07-02 14:35 ` Mike Rapoport
2026-07-01 13:57 ` [PATCH 2/4] ice: use kzalloc() to allocate staging buffer for reading from GNSS Mike Rapoport (Microsoft)
2026-07-02 13:49 ` Przemek Kitszel [this message]
2026-07-02 14:40 ` Mike Rapoport
2026-07-01 13:57 ` [PATCH 3/4] sfc/siena: use kmalloc() to allocate logging buffer Mike Rapoport (Microsoft)
2026-07-01 17:01 ` Edward Cree
2026-07-01 13:57 ` [PATCH 4/4] sfc: " Mike Rapoport (Microsoft)
2026-07-01 16:59 ` Edward Cree
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=d2c75404-a87f-4bb6-b17c-c921d08a1f15@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-net-drivers@amd.com \
--cc=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rppt@kernel.org \
--cc=skalluru@marvell.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