<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>All,</div><div><br></div><div>Me,
Csaba and Manoj are presenting our experiences with using FUSE as an
interface for Glusterfs at Vault'19 [1]. One of the areas Glusterfs has
faced difficulties is with memory management. One of the reasons for
high memory consumption has been the amount of memory consumed by
glusterfs mount process to maintain the inodes looked up by the kernel.
Though we've a solution [2] for this problem, things would've been much
easier and effective if Glusterfs was in kernel space (for the case of
memory management). In kernel space, the memory consumed by inodes would
be accounted for kernel's inode cache and hence kernel memory
management would manage the inodes more effectively and intelligently.
However, being in userspace there is no way to account the memory
consumed for an inode in user space and hence only a very small part of
the memory gets accounted (the inode maintained by fuse kernel module).</div><div><br></div><div>The
objective of this mail is to collect more cases/user issues/bugs such
as these so that we can present them as evidence. I am currently aware
of a tracker issue [3] which covers the issue I mentioned above.</div><div><br></div><div>Also, if you are aware of any other memory management issues, we are interested in them.<br></div><div><br></div><div>[1] <a href="https://www.usenix.org/conference/vault19/presentation/pillai" target="_blank">https://www.usenix.org/conference/vault19/presentation/pillai</a></div><div>[2] <a href="https://review.gluster.org/#/c/glusterfs/+/19778/" target="_blank">https://review.gluster.org/#/c/glusterfs/+/19778/</a></div><div>[3] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1647277" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1647277</a><div class="gmail-adL"><br></div></div></div></div></div></div></div>