lkml.org 
[lkml]   [2019]   [Mar]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC v2 1/3] dma-buf: give each buffer a full-fledged inode
On Fri, Mar 22, 2019 at 11:02:55AM -0400, Joel Fernandes wrote:
> On Thu, Mar 21, 2019 at 07:51:33PM -0700, Chenbo Feng wrote:
> > From: Greg Hackmann <ghackmann@google.com>
> >
> > By traversing /proc/*/fd and /proc/*/map_files, processes with CAP_ADMIN
> > can get a lot of fine-grained data about how shmem buffers are shared
> > among processes. stat(2) on each entry gives the caller a unique
> > ID (st_ino), the buffer's size (st_size), and even the number of pages
> > currently charged to the buffer (st_blocks / 512).
> >
> > In contrast, all dma-bufs share the same anonymous inode. So while we
> > can count how many dma-buf fds or mappings a process has, we can't get
> > the size of the backing buffers or tell if two entries point to the same
> > dma-buf. On systems with debugfs, we can get a per-buffer breakdown of
> > size and reference count, but can't tell which processes are actually
> > holding the references to each buffer.
> >
> > Replace the singleton inode with full-fledged inodes allocated by
> > alloc_anon_inode(). This involves creating and mounting a
> > mini-pseudo-filesystem for dma-buf, following the example in fs/aio.c.
> >
> > Signed-off-by: Greg Hackmann <ghackmann@google.com>
>
> I believe Greg's address needs to be updated on this patch otherwise the
> emails would just bounce, no? I removed it from the CC list. You can still
> keep the SOB I guess but remove it from the CC list when sending.
>
> Also about the minifs, just playing devil's advocate for why this is needed.
>
> Since you are already adding the size information to /proc/pid/fdinfo/<fd> ,
> can just that not be used to get the size of the buffer? What is the benefit
> of getting this from stat? The other way to get the size would be through
> another IOCTL and that can be used to return other unique-ness related metadata
> as well. Neither of these need creation of a dedicated inode per dmabuf.

Can you give an example of "unique-ness related data" here? The inode seems
like the best fit cause its already unique, no?

> Imagine 1000s of dmabuf created in a system with rich graphics, then you have
> inode allocated per dmabuf, sounds wasteful to me if not needed.

It is, in fact, needed. The only way to differentiate a buffer owned by the
same process of the same size (which is very common) is via this unique
inode. Benefits of attaching the buffer metadata to the inode are that now
the metadata can be easily queried from userspace using stat(2) too.

> You are also
> adding the name per buffer, which can also be used to distinguish between
> different buffers if that's the issue.

The name is not unique, unless its decided by the kernel (which we don't want).
The names are coming in from user space in this case and are generally used
to track the "type / use case" of the buffer for debugging / triaging
purposes. We didn't want to rely on user space to give each buffer a unique
name, neither do we want to be responsible for generating one.

>
> Also what is the benefit of having st_blocks from stat? AFAIK, that is the
> same as the buffer's size which does not change for the lifetime of the
> buffer. In your patch you're doing this when 'struct file' is created which
> AIUI is what reflects in the st_blocks:
> + inode_set_bytes(inode, dmabuf->size);

Can some of the use cases / data be trimmed down? I think so. For example, I
never understood what we do with map_files here (or why). It is perfectly
fine to just get the data from /proc/<pid>/fd and /proc/<pid>/maps. I guess
the map_files bit is for consistency?

>
> Note that creating a new mount and allocating inode for each buf will consume
> more kernel memory than before. Has there been a study of how much this is in
> reality? Like by running a game? This is the point of using
> anon_inode_getfile in the first place is to not have this wastage.

Its not "wastage" if its being used to track memeory IMHO. To give
some perspective, On Pixel 2 after fresh reboot + launch camera, we track
about 444 dmabuf objects with this that amounted to about 568573952
untracked memory. The cost of 444 'struct inode' compared to the 500+MB of
untrackable memory is miniscule.

May be, to make it generic, we make the tracking part optional somehow to
avoid the apparent wastage on other systems.

>
> I am not against adding of inode per buffer, but I think we should have this
> debate and make the right design choice here for what we really need.

sure.

- ssp
>
> thanks!
>
> - Joel
>
>
> > Signed-off-by: Chenbo Feng <fengc@google.com>
> > ---
> > drivers/dma-buf/dma-buf.c | 63 ++++++++++++++++++++++++++++++++++----
> > include/uapi/linux/magic.h | 1 +
> > 2 files changed, 58 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dma-buf.c
> > index 7c858020d14b..ffd5a2ad7d6f 100644
> > --- a/drivers/dma-buf/dma-buf.c
> > +++ b/drivers/dma-buf/dma-buf.c
> > @@ -34,8 +34,10 @@
> > #include <linux/poll.h>
> > #include <linux/reservation.h>
> > #include <linux/mm.h>
> > +#include <linux/mount.h>
> >
> > #include <uapi/linux/dma-buf.h>
> > +#include <uapi/linux/magic.h>
> >
> > static inline int is_dma_buf_file(struct file *);
> >
> > @@ -46,6 +48,25 @@ struct dma_buf_list {
> >
> > static struct dma_buf_list db_list;
> >
> > +static const struct dentry_operations dma_buf_dentry_ops = {
> > + .d_dname = simple_dname,
> > +};
> > +
> > +static struct vfsmount *dma_buf_mnt;
> > +
> > +static struct dentry *dma_buf_fs_mount(struct file_system_type *fs_type,
> > + int flags, const char *name, void *data)
> > +{
> > + return mount_pseudo(fs_type, "dmabuf:", NULL, &dma_buf_dentry_ops,
> > + DMA_BUF_MAGIC);
> > +}
> > +
> > +static struct file_system_type dma_buf_fs_type = {
> > + .name = "dmabuf",
> > + .mount = dma_buf_fs_mount,
> > + .kill_sb = kill_anon_super,
> > +};
> > +
> > static int dma_buf_release(struct inode *inode, struct file *file)
> > {
> > struct dma_buf *dmabuf;
> > @@ -338,6 +359,31 @@ static inline int is_dma_buf_file(struct file *file)
> > return file->f_op == &dma_buf_fops;
> > }
> >
> > +static struct file *dma_buf_getfile(struct dma_buf *dmabuf, int flags)
> > +{
> > + struct file *file;
> > + struct inode *inode = alloc_anon_inode(dma_buf_mnt->mnt_sb);
> > +
> > + if (IS_ERR(inode))
> > + return ERR_CAST(inode);
> > +
> > + inode->i_size = dmabuf->size;
> > + inode_set_bytes(inode, dmabuf->size);
> > +
> > + file = alloc_file_pseudo(inode, dma_buf_mnt, "dmabuf",
> > + flags, &dma_buf_fops);
> > + if (IS_ERR(file))
> > + goto err_alloc_file;
> > + file->f_flags = flags & (O_ACCMODE | O_NONBLOCK);
> > + file->private_data = dmabuf;
> > +
> > + return file;
> > +
> > +err_alloc_file:
> > + iput(inode);
> > + return file;
> > +}
> > +
> > /**
> > * DOC: dma buf device access
> > *
> > @@ -433,8 +479,7 @@ struct dma_buf *dma_buf_export(const struct dma_buf_export_info *exp_info)
> > }
> > dmabuf->resv = resv;
> >
> > - file = anon_inode_getfile("dmabuf", &dma_buf_fops, dmabuf,
> > - exp_info->flags);
> > + file = dma_buf_getfile(dmabuf, exp_info->flags);
> > if (IS_ERR(file)) {
> > ret = PTR_ERR(file);
> > goto err_dmabuf;
> > @@ -1025,8 +1070,8 @@ static int dma_buf_debug_show(struct seq_file *s, void *unused)
> > return ret;
> >
> > seq_puts(s, "\nDma-buf Objects:\n");
> > - seq_printf(s, "%-8s\t%-8s\t%-8s\t%-8s\texp_name\n",
> > - "size", "flags", "mode", "count");
> > + seq_printf(s, "%-8s\t%-8s\t%-8s\t%-8s\texp_name\t%-8s\n",
> > + "size", "flags", "mode", "count", "ino");
> >
> > list_for_each_entry(buf_obj, &db_list.head, list_node) {
> > ret = mutex_lock_interruptible(&buf_obj->lock);
> > @@ -1037,11 +1082,12 @@ static int dma_buf_debug_show(struct seq_file *s, void *unused)
> > continue;
> > }
> >
> > - seq_printf(s, "%08zu\t%08x\t%08x\t%08ld\t%s\n",
> > + seq_printf(s, "%08zu\t%08x\t%08x\t%08ld\t%s\t%08lu\n",
> > buf_obj->size,
> > buf_obj->file->f_flags, buf_obj->file->f_mode,
> > file_count(buf_obj->file),
> > - buf_obj->exp_name);
> > + buf_obj->exp_name,
> > + file_inode(buf_obj->file)->i_ino);
> >
> > robj = buf_obj->resv;
> > while (true) {
> > @@ -1136,6 +1182,10 @@ static inline void dma_buf_uninit_debugfs(void)
> >
> > static int __init dma_buf_init(void)
> > {
> > + dma_buf_mnt = kern_mount(&dma_buf_fs_type);
> > + if (IS_ERR(dma_buf_mnt))
> > + return PTR_ERR(dma_buf_mnt);
> > +
> > mutex_init(&db_list.lock);
> > INIT_LIST_HEAD(&db_list.head);
> > dma_buf_init_debugfs();
> > @@ -1146,5 +1196,6 @@ subsys_initcall(dma_buf_init);
> > static void __exit dma_buf_deinit(void)
> > {
> > dma_buf_uninit_debugfs();
> > + kern_unmount(dma_buf_mnt);
> > }
> > __exitcall(dma_buf_deinit);
> > diff --git a/include/uapi/linux/magic.h b/include/uapi/linux/magic.h
> > index f8c00045d537..665e18627f78 100644
> > --- a/include/uapi/linux/magic.h
> > +++ b/include/uapi/linux/magic.h
> > @@ -91,5 +91,6 @@
> > #define UDF_SUPER_MAGIC 0x15013346
> > #define BALLOON_KVM_MAGIC 0x13661366
> > #define ZSMALLOC_MAGIC 0x58295829
> > +#define DMA_BUF_MAGIC 0x444d4142 /* "DMAB" */
> >
> > #endif /* __LINUX_MAGIC_H__ */
> > --
> > 2.21.0.225.g810b269d1ac-goog
> >
>
>

\
 
 \ /
  Last update: 2019-03-24 18:57    [W:0.062 / U:13.264 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site