From: patchwork-bot+netdevbpf@kernel.org
To: T.J. Mercier <tjmercier@google.com>
Cc: sumit.semwal@linaro.org, christian.koenig@amd.com,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, skhan@linuxfoundation.org,
alexei.starovoitov@gmail.com, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, android-mm@google.com,
simona@ffwll.ch, eddyz87@gmail.com, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
jolsa@kernel.org, mykolal@fb.com, shuah@kernel.org,
song@kernel.org
Subject: Re: [PATCH bpf-next v7 0/5] Replace CONFIG_DMABUF_SYSFS_STATS with BPF
Date: Tue, 27 May 2025 17:00:36 +0000 [thread overview]
Message-ID: <174836523626.1711047.17059127767778339738.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250522230429.941193-1-tjmercier@google.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 22 May 2025 23:04:24 +0000 you wrote:
> Until CONFIG_DMABUF_SYSFS_STATS was added [1] it was only possible to
> perform per-buffer accounting with debugfs which is not suitable for
> production environments. Eventually we discovered the overhead with
> per-buffer sysfs file creation/removal was significantly impacting
> allocation and free times, and exacerbated kernfs lock contention. [2]
> dma_buf_stats_setup() is responsible for 39% of single-page buffer
> creation duration, or 74% of single-page dma_buf_export() duration when
> stressing dmabuf allocations and frees.
>
> [...]
Here is the summary with links:
- [bpf-next,v7,1/5] dma-buf: Rename debugfs symbols
https://git.kernel.org/bpf/bpf-next/c/89f9dba365e1
- [bpf-next,v7,2/5] bpf: Add dmabuf iterator
https://git.kernel.org/bpf/bpf-next/c/76ea95534995
- [bpf-next,v7,3/5] bpf: Add open coded dmabuf iterator
https://git.kernel.org/bpf/bpf-next/c/6eab7ac7c5ee
- [bpf-next,v7,4/5] selftests/bpf: Add test for dmabuf_iter
https://git.kernel.org/bpf/bpf-next/c/ae5d2c59ecd7
- [bpf-next,v7,5/5] selftests/bpf: Add test for open coded dmabuf_iter
https://git.kernel.org/bpf/bpf-next/c/7594dcb71ff8
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:[~2025-05-27 17:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 23:04 [PATCH bpf-next v7 0/5] Replace CONFIG_DMABUF_SYSFS_STATS with BPF T.J. Mercier
2025-05-22 23:04 ` [PATCH bpf-next v7 1/5] dma-buf: Rename debugfs symbols T.J. Mercier
2025-05-22 23:04 ` [PATCH bpf-next v7 2/5] bpf: Add dmabuf iterator T.J. Mercier
2025-05-22 23:04 ` [PATCH bpf-next v7 3/5] bpf: Add open coded " T.J. Mercier
2025-05-22 23:04 ` [PATCH bpf-next v7 4/5] selftests/bpf: Add test for dmabuf_iter T.J. Mercier
2025-05-22 23:04 ` [PATCH bpf-next v7 5/5] selftests/bpf: Add test for open coded dmabuf_iter T.J. Mercier
2025-05-27 17:00 ` 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=174836523626.1711047.17059127767778339738.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=android-mm@google.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=christian.koenig@amd.com \
--cc=daniel@iogearbox.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=eddyz87@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.org \
--cc=song@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tjmercier@google.com \
--cc=yonghong.song@linux.dev \
/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