lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 30 Nov 2023 22:55:24 -0800
From: Jakub Kicinski <>
To: Alexander Lobakin <>
Cc: "David S. Miller" <>, Eric Dumazet
 <>, Paolo Abeni <>, Maciej Fijalkowski
 <>, Michal Kubiak <>,
 Larysa Zaremba <>, Alexander Duyck
 <>, Yunsheng Lin <>, "David
 Christensen" <>, Jesper Dangaard Brouer
 <>, Ilias Apalodimas <>, "Paul
 Menzel" <>, <>,
 <>, <>
Subject: Re: [PATCH net-next v5 13/14] libie: add per-queue Page Pool stats

On Thu, 30 Nov 2023 17:45:10 +0100 Alexander Lobakin wrote:
> > Meh, this way the stats won't survive ifdown/ifup cycles as usually
> > page_pools get destroyed on ifdown :z
> > In that patch, I backup the PP stats to a device-lifetime container when
> > the pool gets destroyed, maybe we could do something similar?  
> I still can pull the PP stats to the driver before destroying it, but
> there's no way to tell the PP I have some archived stats for it. Maybe
> we could have page_pool_params_slow::get_stats() or smth like this?

Why do you think the historic values matter?
User space monitoring will care about incremental values.
It's not like for page pool we need to match the Rx packet count.

Powered by blists - more mailing lists