From: Randy Dunlap <rdunlap@infradead.org>
To: Kalesh Singh <kaleshsingh@google.com>
Cc: jannh@google.com, jeffv@google.com, keescook@chromium.org,
surenb@google.com, minchan@kernel.org, hridya@google.com,
kernel-team@android.com, "Alexey Dobriyan" <adobriyan@gmail.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
"Michal Hocko" <mhocko@suse.com>,
"Alexey Gladkov" <gladkov.alexey@gmail.com>,
"Anand K Mistry" <amistry@google.com>, NeilBrown <neilb@suse.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"Michel Lespinasse" <walken@google.com>,
"Bernd Edlinger" <bernd.edlinger@hotmail.de>,
"Andrei Vagin" <avagin@gmail.com>,
"Yafang Shao" <laoar.shao@gmail.com>,
"Christian Brauner" <christian.brauner@ubuntu.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH v3 2/2] dmabuf: Add dmabuf inode number to /proc/*/fdinfo
Date: Thu, 4 Feb 2021 18:36:43 -0800 [thread overview]
Message-ID: <b2d08c27-ae9b-16ed-3500-a4a724d563ef@infradead.org> (raw)
In-Reply-To: <20210205022328.481524-2-kaleshsingh@google.com>
On 2/4/21 6:23 PM, Kalesh Singh wrote:
> If a FD refers to a DMA buffer add the DMA buffer inode number to
> /proc/<pid>/fdinfo/<FD> and /proc/<pid>/task/<tid>/fdindo/<FD>.
>
> The dmabuf inode number allows userspace to uniquely identify the buffer
> and avoids a dependency on /proc/<pid>/fd/* when accounting per-process
> DMA buffer sizes.
>
> Signed-off-by: Kalesh Singh <kaleshsingh@google.com>
> ---
> Changes in v3:
> - Add documentation in proc.rst
Hi,
Thanks for the doc update.
> Changes in v2:
> - Update patch description
>
> Documentation/filesystems/proc.rst | 17 +++++++++++++++++
> drivers/dma-buf/dma-buf.c | 1 +
> 2 files changed, 18 insertions(+)
>
Acked-by: Randy Dunlap <rdunlap@infradead.org> # for Documentation/filesystems/proc.rst
--
~Randy
next prev parent reply other threads:[~2021-02-05 2:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 2:23 [PATCH v3 1/2] procfs: Allow reading fdinfo with PTRACE_MODE_READ Kalesh Singh
2021-02-05 2:23 ` [PATCH v3 2/2] dmabuf: Add dmabuf inode number to /proc/*/fdinfo Kalesh Singh
2021-02-05 2:36 ` Randy Dunlap [this message]
2021-02-05 7:56 ` Christian König
2021-02-05 15:13 ` Kalesh Singh
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=b2d08c27-ae9b-16ed-3500-a4a724d563ef@infradead.org \
--to=rdunlap@infradead.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=amistry@google.com \
--cc=avagin@gmail.com \
--cc=bernd.edlinger@hotmail.de \
--cc=christian.brauner@ubuntu.com \
--cc=christian.koenig@amd.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=ebiederm@xmission.com \
--cc=gladkov.alexey@gmail.com \
--cc=hridya@google.com \
--cc=jannh@google.com \
--cc=jeffv@google.com \
--cc=kaleshsingh@google.com \
--cc=keescook@chromium.org \
--cc=kernel-team@android.com \
--cc=laoar.shao@gmail.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=neilb@suse.de \
--cc=sumit.semwal@linaro.org \
--cc=surenb@google.com \
--cc=walken@google.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
all inboxes | Powered by JetHome®