All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <jbrouer@redhat.com>
To: Joe Damato <jdamato@fastly.com>, netdev@vger.kernel.org
Cc: brouer@redhat.com, kuba@kernel.org, davem@davemloft.net,
	ilias.apalodimas@linaro.org, hawk@kernel.org
Subject: Re: [PATCH net-next 0/6] net: page_pool: Add page_pool stat counters
Date: Thu, 27 Jan 2022 09:51:48 +0100	[thread overview]
Message-ID: <c7945726-6d6a-2361-3c5a-1f9e3187683a@redhat.com> (raw)
In-Reply-To: <1643237300-44904-1-git-send-email-jdamato@fastly.com>



On 26/01/2022 23.48, Joe Damato wrote:
> Greetings:
> 
> This series adds some stat counters for the page_pool allocation path which
> help to track:
> 
> 	- fast path allocations
> 	- slow path order-0 allocations
> 	- slow path high order allocations
> 	- refills which failed due to an empty ptr ring, forcing a slow
> 	  path allocation
> 	- allocations fulfilled via successful refill
> 	- pages which cannot be added to the cache because of numa mismatch
> 	  (i.e. waived)
> 
> Some static inline wrappers are provided for accessing these stats. The
> intention is that drivers which use the page_pool API can, if they choose,
> use this stats API.

You are adding (always on) counters to a critical fast-path, that 
drivers uses for the XDP_DROP use-case.

I want to see performance measurements as documentation, showing this is 
not causing a slow-down.

I have some performance tests here[1]:
  [1] 
https://github.com/netoptimizer/prototype-kernel/tree/master/kernel/lib

Look at:
  - bench_page_pool_simple.c and
  - bench_page_pool_cross_cpu.c

How to use + build this[2]:
  [2] 
https://prototype-kernel.readthedocs.io/en/latest/prototype-kernel/build-process.html

> It assumed that the API consumer will ensure the page_pool is not destroyed
> during calls to the stats API.
> 
> If this series is accepted, I'll submit a follow up patch which will export
> these stats per RX-ring via ethtool in a driver which uses the page_pool
> API.
> 
> Joe Damato (6):
>    net: page_pool: Add alloc stats and fast path stat
>    net: page_pool: Add a stat for the slow alloc path
>    net: page_pool: Add a high order alloc stat
>    net: page_pool: Add stat tracking empty ring
>    net: page_pool: Add stat tracking cache refills.
>    net: page_pool: Add a stat tracking waived pages.
> 
>   include/net/page_pool.h | 82 +++++++++++++++++++++++++++++++++++++++++++++++++
>   net/core/page_pool.c    | 15 +++++++--
>   2 files changed, 94 insertions(+), 3 deletions(-)
> 


  parent reply	other threads:[~2022-01-27  8:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 22:48 [PATCH net-next 0/6] net: page_pool: Add page_pool stat counters Joe Damato
2022-01-26 22:48 ` [PATCH 1/6] net: page_pool: Add alloc stats and fast path stat Joe Damato
2022-01-27 16:32   ` Jakub Kicinski
2022-01-27 21:11     ` Joe Damato
2022-02-02 14:14   ` Jesper Dangaard Brouer
2022-01-26 22:48 ` [PATCH net-next 2/6] net: page_pool: Add a stat for the slow alloc path Joe Damato
2022-01-26 22:48 ` [PATCH net-next 3/6] net: page_pool: Add a high order alloc stat Joe Damato
2022-01-26 22:48 ` [PATCH net-next 4/6] net: page_pool: Add stat tracking empty ring Joe Damato
2022-01-26 22:48 ` [PATCH net-next 5/6] net: page_pool: Add stat tracking cache refills Joe Damato
2022-01-26 22:48 ` [PATCH 6/6] net: page_pool: Add a stat tracking waived pages Joe Damato
2022-01-27  8:51 ` Jesper Dangaard Brouer [this message]
2022-01-27 21:08   ` [PATCH net-next 0/6] net: page_pool: Add page_pool stat counters Joe Damato
2022-02-02 14:04     ` Jesper Dangaard Brouer
2022-01-27  9:08 ` Ilias Apalodimas
2022-01-27 23:55   ` Joe Damato
2022-01-29 14:07     ` Ilias Apalodimas
2022-01-29 18:07       ` Joe Damato

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=c7945726-6d6a-2361-3c5a-1f9e3187683a@redhat.com \
    --to=jbrouer@redhat.com \
    --cc=brouer@redhat.com \
    --cc=davem@davemloft.net \
    --cc=hawk@kernel.org \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jdamato@fastly.com \
    --cc=kuba@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.