[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <815485547a20f80f6dce991b76a7b60aebf1a716.camel@redhat.com>
Date: Tue, 21 Feb 2023 10:12:56 +0100
From: Paolo Abeni <pabeni@...hat.com>
To: Ilias Apalodimas <ilias.apalodimas@...aro.org>,
netdev@...r.kernel.org
Cc: alexander.duyck@...il.com, Alexander Duyck <alexanderduyck@...com>,
Jesper Dangaard Brouer <hawk@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] page_pool: add a comment explaining the fragment
counter usage
On Sat, 2023-02-18 at 00:21 +0200, Ilias Apalodimas wrote:
> When reading the page_pool code the first impression is that keeping
> two separate counters, one being the page refcnt and the other being
> fragment pp_frag_count, is counter-intuitive.
>
> However without that fragment counter we don't know when to reliably
> destroy or sync the outstanding DMA mappings. So let's add a comment
> explaining this part.
>
> Reviewed-by: Alexander Duyck <alexanderduyck@...com>
> Signed-off-by: Ilias Apalodimas <ilias.apalodimas@...aro.org>
# Form letter - net-next is closed
The merge window for v6.3 has begun and therefore net-next is closed
for new drivers, features, code refactoring and optimizations.
We are currently accepting bug fixes only.
Please repost when net-next reopens after Mar 6th.
RFC patches sent for review only are obviously welcome at any time.
Powered by blists - more mailing lists