From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Ilias Apalodimas <ilias.apalodimas@linaro.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
netdev@vger.kernel.org, lorenzo.bianconi@redhat.com,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
thomas.petazzoni@bootlin.com, linux@armlinux.org.uk,
jbrouer@redhat.com, jdamato@fastly.com
Subject: Re: [PATCH net-next] net: mvneta: add support for page_pool_get_stats
Date: Wed, 6 Apr 2022 15:05:26 +0200 [thread overview]
Message-ID: <Yk2QFmvQOSiL8WKH@lore-desk> (raw)
In-Reply-To: <CAC_iWjLD8_PsC=AHqR+FeH3qA-TWfWRDfah+7QHXS6dGx7AJPA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
> Hi Andrew
>
> On Wed, 6 Apr 2022 at 15:49, Andrew Lunn <andrew@lunn.ch> wrote:
> >
> > On Tue, Apr 05, 2022 at 10:32:12PM +0200, Lorenzo Bianconi wrote:
> > > Introduce support for the page_pool_get_stats API to mvneta driver.
> > > If CONFIG_PAGE_POOL_STATS is enabled, ethtool will report page pool
> > > stats.
> >
> > Hi Lorenzo
> >
> > There are a lot of #ifdef in this patch. They are generally not
> > liked. What does the patch actually depend on? mnveta has a select
> > PAGE_POOL so the page pool itself should always be available?
>
> The stats are on a different Kconfig since we wanted to allow people
> opt out if they were worried about performance. However this is not a
> 10gbit interface and I doubt there will be any measurable hit. I
> think selecting PAGE_POOL_STATS for the driver makes sense and will
> make the code easier to follow.
Hi Andrew and Ilias,
I just kept the same approach used for mlx driver but I am fine to always
select PAGE_POOL_STATS for mvneta. I will fix it in v2.
Regards,
Lorenzo
>
> Thanks
> /Ilias
> >
> > Andrew
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-04-06 15:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 20:32 [PATCH net-next] net: mvneta: add support for page_pool_get_stats Lorenzo Bianconi
2022-04-06 12:49 ` Andrew Lunn
2022-04-06 12:53 ` Ilias Apalodimas
2022-04-06 13:05 ` Lorenzo Bianconi [this message]
2022-04-06 13:38 ` Andrew Lunn
2022-04-06 14:02 ` Lorenzo Bianconi
2022-04-06 23:01 ` Joe Damato
2022-04-06 23:36 ` Andrew Lunn
2022-04-07 16:48 ` Lorenzo Bianconi
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=Yk2QFmvQOSiL8WKH@lore-desk \
--to=lorenzo@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=ilias.apalodimas@linaro.org \
--cc=jbrouer@redhat.com \
--cc=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lorenzo.bianconi@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=thomas.petazzoni@bootlin.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;
as well as URLs for NNTP newsgroup(s).