From: patchwork-bot+netdevbpf@kernel.org
To: Larysa Zaremba <larysa.zaremba@intel.com>
Cc: bpf@vger.kernel.org, bjorn@kernel.org, magnus.karlsson@intel.com,
maciej.fijalkowski@intel.com, jonathan.lemon@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, ast@kernel.org, daniel@iogearbox.net,
hawk@kernel.org, john.fastabend@gmail.com, horms@kernel.org,
przemyslaw.kitszel@intel.com, jacob.e.keller@intel.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
alasdair.mcwilliam@outlook.com
Subject: Re: [PATCH bpf] xsk: always clear DMA mapping information when unmapping the pool
Date: Mon, 25 Nov 2024 22:30:35 +0000 [thread overview]
Message-ID: <173257383550.4058254.12806548531670345328.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241122112912.89881-1-larysa.zaremba@intel.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 22 Nov 2024 12:29:09 +0100 you wrote:
> When the umem is shared, the DMA mapping is also shared between the xsk
> pools, therefore it should stay valid as long as at least 1 user remains.
> However, the pool also keeps the copies of DMA-related information that are
> initialized in the same way in xp_init_dma_info(), but cleared by
> xp_dma_unmap() only for the last remaining pool, this causes the problems
> below.
>
> [...]
Here is the summary with links:
- [bpf] xsk: always clear DMA mapping information when unmapping the pool
https://git.kernel.org/bpf/bpf/c/ac9a48a6f161
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-11-25 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 11:29 [PATCH bpf] xsk: always clear DMA mapping information when unmapping the pool Larysa Zaremba
2024-11-25 22:30 ` patchwork-bot+netdevbpf [this message]
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=173257383550.4058254.12806548531670345328.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alasdair.mcwilliam@outlook.com \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=john.fastabend@gmail.com \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=larysa.zaremba@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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