From: Jakub Kicinski <kuba@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Lorenzo Bianconi <lorenzo@kernel.org>,
netdev@vger.kernel.org, ilias.apalodimas@linaro.org,
hawk@kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, corbet@lwn.net, linux-doc@vger.kernel.org,
jbrouer@redhat.com, lorenzo.bianconi@redhat.com
Subject: Re: [PATCH net-next] Documentation: update networking/page_pool.rst with ethtool APIs
Date: Mon, 9 May 2022 09:13:30 -0700 [thread overview]
Message-ID: <20220509091330.4e8c6d05@kernel.org> (raw)
In-Reply-To: <YnkIJn2BhSzyfQjh@lunn.ch>
On Mon, 9 May 2022 14:25:10 +0200 Andrew Lunn wrote:
> On Mon, May 09, 2022 at 12:00:01PM +0200, Lorenzo Bianconi wrote:
> > Update page_pool documentation with page_pool ethtool stats APIs.
> >
> > Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
> > ---
> > Documentation/networking/page_pool.rst | 23 +++++++++++++++++++++++
> > 1 file changed, 23 insertions(+)
> >
> > diff --git a/Documentation/networking/page_pool.rst b/Documentation/networking/page_pool.rst
> > index 5db8c263b0c6..ef5e18cf7cdf 100644
> > --- a/Documentation/networking/page_pool.rst
> > +++ b/Documentation/networking/page_pool.rst
> > @@ -146,6 +146,29 @@ The ``struct page_pool_recycle_stats`` has the following fields:
> > * ``ring_full``: page released from page pool because the ptr ring was full
> > * ``released_refcnt``: page released (and not recycled) because refcnt > 1
> >
> > +The following APIs can be used to report page_pool stats through ethtool and
> > +avoid code duplication in each driver:
> > +
> > +* page_pool_ethtool_stats_get_strings(): reports page_pool ethtool stats
> > + strings according to the ``struct page_pool_stats``
> > + * ``rx_pp_alloc_fast``
> > + * ``rx_pp_alloc_slow``
> > + * ``rx_pp_alloc_slow_ho``
> > + * ``rx_pp_alloc_empty``
> > + * ``rx_pp_alloc_refill``
> > + * ``rx_pp_alloc_waive``
> > + * ``rx_pp_recycle_cached``
> > + * ``rx_pp_recycle_cache_full``
> > + * ``rx_pp_recycle_ring``
> > + * ``rx_pp_recycle_ring_full``
> > + * ``rx_pp_recycle_released_ref``
>
> My knowledge of Sphinx is pretty poor. Is it possible to put this list
> next to the actual definition and cross reference it? When new
> counters are added, they are more likely to be added to the list, if
> the list is nearby.
We can render kdoc into documentation. Not sure what's most suitable
here.
BTW does ``struct xyz`` result in correct linking to the kdoc like
:c:type:`xyz` would or I think these days also pure struct xyz?
next prev parent reply other threads:[~2022-05-09 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 10:00 [PATCH net-next] Documentation: update networking/page_pool.rst with ethtool APIs Lorenzo Bianconi
2022-05-09 12:25 ` Andrew Lunn
2022-05-09 16:13 ` Jakub Kicinski [this message]
2022-05-09 18:28 ` Jonathan Corbet
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=20220509091330.4e8c6d05@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=jbrouer@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=lorenzo@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;
as well as URLs for NNTP newsgroup(s).