From: Joe Damato <jdamato@fastly.com>
To: Greg Thelen <gthelen@google.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] eth: mlx4: select PAGE_POOL
Date: Wed, 2 Apr 2025 08:50:00 -0700 [thread overview]
Message-ID: <Z-1cqKd-2avzWQtI@LQ3V64L9R2> (raw)
In-Reply-To: <20250401015315.2306092-1-gthelen@google.com>
On Mon, Mar 31, 2025 at 06:53:15PM -0700, Greg Thelen wrote:
> With commit 8533b14b3d65 ("eth: mlx4: create a page pool for Rx") mlx4
> started using functions guarded by PAGE_POOL. This change introduced
> build errors when CONFIG_MLX4_EN is set but CONFIG_PAGE_POOL is not:
>
> ld: vmlinux.o: in function `mlx4_en_alloc_frags':
> en_rx.c:(.text+0xa5eaf9): undefined reference to `page_pool_alloc_pages'
> ld: vmlinux.o: in function `mlx4_en_create_rx_ring':
> (.text+0xa5ee91): undefined reference to `page_pool_create'
>
> Make MLX4_EN select PAGE_POOL to fix the ml;x4 build errors.
>
> Fixes: 8533b14b3d65 ("eth: mlx4: create a page pool for Rx")
> Signed-off-by: Greg Thelen <gthelen@google.com>
> ---
> drivers/net/ethernet/mellanox/mlx4/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/ethernet/mellanox/mlx4/Kconfig b/drivers/net/ethernet/mellanox/mlx4/Kconfig
> index 825e05fb8607..0b1cb340206f 100644
> --- a/drivers/net/ethernet/mellanox/mlx4/Kconfig
> +++ b/drivers/net/ethernet/mellanox/mlx4/Kconfig
> @@ -7,6 +7,7 @@ config MLX4_EN
> tristate "Mellanox Technologies 1/10/40Gbit Ethernet support"
> depends on PCI && NETDEVICES && ETHERNET && INET
> depends on PTP_1588_CLOCK_OPTIONAL
> + select PAGE_POOL
I didn't look, but I assume that mlx4 does not use page pool stats?
If it does, there might be a follow-up change to select
PAGE_POOL_STATS?
Reviewed-by: Joe Damato <jdamato@fastly.com>
next prev parent reply other threads:[~2025-04-02 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 1:53 [PATCH] eth: mlx4: select PAGE_POOL Greg Thelen
2025-04-02 15:50 ` Joe Damato [this message]
2025-04-02 23:40 ` 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=Z-1cqKd-2avzWQtI@LQ3V64L9R2 \
--to=jdamato@fastly.com \
--cc=gthelen@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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