Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v3] page_pool: add a comment explaining the fragment counter
 usage
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <167700061770.3298.14628579257086462902.git-patchwork-notify@kernel.org>
Date:   Tue, 21 Feb 2023 17:30:17 +0000
References: <20230217222130.85205-1-ilias.apalodimas@linaro.org>
In-Reply-To: <20230217222130.85205-1-ilias.apalodimas@linaro.org>
To:     Ilias Apalodimas <ilias.apalodimas@linaro.org>
Cc:     netdev@vger.kernel.org, alexander.duyck@gmail.com,
        alexanderduyck@fb.com, hawk@kernel.org, davem@davemloft.net,
        edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
        linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Sat, 18 Feb 2023 00:21:30 +0200 you 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.
> 
> [...]

Here is the summary with links:
  - [v3] page_pool: add a comment explaining the fragment counter usage
    https://git.kernel.org/netdev/net-next/c/4d4266e3fd32

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html