From: Brian Foster <bfoster@redhat.com>
To: Kalesh Singh <kaleshsingh@google.com>
Cc: ckoenig.leichtzumerken@gmail.com, christian.koenig@amd.com,
viro@zeniv.linux.org.uk, hch@infradead.org,
stephen.s.brennan@oracle.com, David.Laight@aculab.com,
ilkos@google.com, tjmercier@google.com, surenb@google.com,
kernel-team@android.com, Jonathan Corbet <corbet@lwn.net>,
Sumit Semwal <sumit.semwal@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Mike Rapoport <rppt@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
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 v2 1/2] procfs: Add 'size' to /proc/<pid>/fdinfo/
Date: Tue, 28 Jun 2022 07:53:51 -0400 [thread overview]
Message-ID: <Yrrrz7MxMu8OoEPU@bfoster> (raw)
In-Reply-To: <20220623220613.3014268-2-kaleshsingh@google.com>
On Thu, Jun 23, 2022 at 03:06:06PM -0700, Kalesh Singh wrote:
> To be able to account the amount of memory a process is keeping pinned
> by open file descriptors add a 'size' field to fdinfo output.
>
> dmabufs fds already expose a 'size' field for this reason, remove this
> and make it a common field for all fds. This allows tracking of
> other types of memory (e.g. memfd and ashmem in Android).
>
> Signed-off-by: Kalesh Singh <kaleshsingh@google.com>
> Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
>
> Changes in v2:
> - Add Christian's Reviewed-by
>
> Changes from rfc:
> - Split adding 'size' and 'path' into a separate patches, per Christian
> - Split fdinfo seq_printf into separate lines, per Christian
> - Fix indentation (use tabs) in documentaion, per Randy
>
> Documentation/filesystems/proc.rst | 12 ++++++++++--
> drivers/dma-buf/dma-buf.c | 1 -
> fs/proc/fd.c | 9 +++++----
> 3 files changed, 15 insertions(+), 7 deletions(-)
>
...
> diff --git a/fs/proc/fd.c b/fs/proc/fd.c
> index 913bef0d2a36..464bc3f55759 100644
> --- a/fs/proc/fd.c
> +++ b/fs/proc/fd.c
> @@ -54,10 +54,11 @@ static int seq_show(struct seq_file *m, void *v)
> if (ret)
> return ret;
>
> - seq_printf(m, "pos:\t%lli\nflags:\t0%o\nmnt_id:\t%i\nino:\t%lu\n",
> - (long long)file->f_pos, f_flags,
> - real_mount(file->f_path.mnt)->mnt_id,
> - file_inode(file)->i_ino);
> + seq_printf(m, "pos:\t%lli\n", (long long)file->f_pos);
> + seq_printf(m, "flags:\t0%o\n", f_flags);
> + seq_printf(m, "mnt_id:\t%i\n", real_mount(file->f_path.mnt)->mnt_id);
> + seq_printf(m, "ino:\t%lu\n", file_inode(file)->i_ino);
> + seq_printf(m, "size:\t%lli\n", (long long)file_inode(file)->i_size);
Hi Kalesh,
Any reason not to use i_size_read() here?
Also not sure if it matters that much for your use case, but something
worth noting at least with shmem is that one can do something like:
# cat /proc/meminfo | grep Shmem:
Shmem: 764 kB
# xfs_io -fc "falloc -k 0 10m" ./file
# ls -alh file
-rw-------. 1 root root 0 Jun 28 07:22 file
# stat file
File: file
Size: 0 Blocks: 20480 IO Block: 4096 regular empty file
# cat /proc/meminfo | grep Shmem:
Shmem: 11004 kB
... where the resulting memory usage isn't reflected in i_size (but is
is in i_blocks/bytes).
Brian
>
> /* show_fd_locks() never deferences files so a stale value is safe */
> show_fd_locks(m, file, files);
> --
> 2.37.0.rc0.161.g10f37bed90-goog
>
next prev parent reply other threads:[~2022-06-28 11:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 22:06 [PATCH v2 0/2] procfs: Add file path and size to /proc/<pid>/fdinfo Kalesh Singh
2022-06-23 22:06 ` [PATCH v2 1/2] procfs: Add 'size' to /proc/<pid>/fdinfo/ Kalesh Singh
2022-06-28 11:53 ` Brian Foster [this message]
2022-06-28 22:38 ` Kalesh Singh
2022-06-29 12:23 ` Brian Foster
2022-06-29 20:43 ` Kalesh Singh
2022-06-30 11:48 ` Brian Foster
2022-06-30 12:03 ` Brian Foster
2022-06-30 21:30 ` Kalesh Singh
2022-06-23 22:06 ` [PATCH v2 2/2] procfs: Add 'path' " 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=Yrrrz7MxMu8OoEPU@bfoster \
--to=bfoster@redhat.com \
--cc=David.Laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=hannes@cmpxchg.org \
--cc=hch@infradead.org \
--cc=ilkos@google.com \
--cc=kaleshsingh@google.com \
--cc=kernel-team@android.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=mail@christoph.anton.mitterer.name \
--cc=paul.gortmaker@windriver.com \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=stephen.s.brennan@oracle.com \
--cc=sumit.semwal@linaro.org \
--cc=surenb@google.com \
--cc=tjmercier@google.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).