From: Michal Hocko <mhocko@kernel.org>
To: Piotr Sarna <p.sarna@tlen.pl>
Cc: linux-kernel@vger.kernel.org, mike.kravetz@oracle.com,
linux-mm@kvack.org, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] hugetlbfs: add O_TMPFILE support
Date: Tue, 15 Oct 2019 12:50:55 +0200 [thread overview]
Message-ID: <20191015105055.GA24932@dhcp22.suse.cz> (raw)
In-Reply-To: <22c29acf9c51dae17802e1b05c9e5e4051448c5c.1571129593.git.p.sarna@tlen.pl>
On Tue 15-10-19 11:01:12, Piotr Sarna wrote:
> With hugetlbfs, a common pattern for mapping anonymous huge pages
> is to create a temporary file first.
Really? I though that this is normally done by shmget(SHM_HUGETLB) or
mmap(MAP_HUGETLB). Or maybe I misunderstood your definition on anonymous
huge pages.
> Currently libraries like
> libhugetlbfs and seastar create these with a standard mkstemp+unlink
> trick, but it would be more robust to be able to simply pass
> the O_TMPFILE flag to open(). O_TMPFILE is already supported by several
> file systems like ext4 and xfs. The implementation simply uses the existing
> d_tmpfile utility function to instantiate the dcache entry for the file.
>
> Tested manually by successfully creating a temporary file by opening
> it with (O_TMPFILE|O_RDWR) on mounted hugetlbfs and successfully
> mapping 2M huge pages with it. Without the patch, trying to open
> a file with O_TMPFILE results in -ENOSUP.
>
> Signed-off-by: Piotr Sarna <p.sarna@tlen.pl>
> ---
> fs/hugetlbfs/inode.c | 25 ++++++++++++++++++++++---
> 1 file changed, 22 insertions(+), 3 deletions(-)
>
> diff --git a/fs/hugetlbfs/inode.c b/fs/hugetlbfs/inode.c
> index 1dcc57189382..277b7d231db8 100644
> --- a/fs/hugetlbfs/inode.c
> +++ b/fs/hugetlbfs/inode.c
> @@ -815,8 +815,11 @@ static struct inode *hugetlbfs_get_inode(struct super_block *sb,
> /*
> * File creation. Allocate an inode, and we're done..
> */
> -static int hugetlbfs_mknod(struct inode *dir,
> - struct dentry *dentry, umode_t mode, dev_t dev)
> +static int do_hugetlbfs_mknod(struct inode *dir,
> + struct dentry *dentry,
> + umode_t mode,
> + dev_t dev,
> + bool tmpfile)
> {
> struct inode *inode;
> int error = -ENOSPC;
> @@ -824,13 +827,22 @@ static int hugetlbfs_mknod(struct inode *dir,
> inode = hugetlbfs_get_inode(dir->i_sb, dir, mode, dev);
> if (inode) {
> dir->i_ctime = dir->i_mtime = current_time(dir);
> - d_instantiate(dentry, inode);
> + if (tmpfile)
> + d_tmpfile(dentry, inode);
> + else
> + d_instantiate(dentry, inode);
> dget(dentry); /* Extra count - pin the dentry in core */
> error = 0;
> }
> return error;
> }
>
> +static int hugetlbfs_mknod(struct inode *dir,
> + struct dentry *dentry, umode_t mode, dev_t dev)
> +{
> + return do_hugetlbfs_mknod(dir, dentry, mode, dev, false);
> +}
> +
> static int hugetlbfs_mkdir(struct inode *dir, struct dentry *dentry, umode_t mode)
> {
> int retval = hugetlbfs_mknod(dir, dentry, mode | S_IFDIR, 0);
> @@ -844,6 +856,12 @@ static int hugetlbfs_create(struct inode *dir, struct dentry *dentry, umode_t mo
> return hugetlbfs_mknod(dir, dentry, mode | S_IFREG, 0);
> }
>
> +static int hugetlbfs_tmpfile(struct inode *dir,
> + struct dentry *dentry, umode_t mode)
> +{
> + return do_hugetlbfs_mknod(dir, dentry, mode | S_IFREG, 0, true);
> +}
> +
> static int hugetlbfs_symlink(struct inode *dir,
> struct dentry *dentry, const char *symname)
> {
> @@ -1102,6 +1120,7 @@ static const struct inode_operations hugetlbfs_dir_inode_operations = {
> .mknod = hugetlbfs_mknod,
> .rename = simple_rename,
> .setattr = hugetlbfs_setattr,
> + .tmpfile = hugetlbfs_tmpfile,
> };
>
> static const struct inode_operations hugetlbfs_inode_operations = {
> --
> 2.21.0
>
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-10-15 10:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 9:01 [PATCH] hugetlbfs: add O_TMPFILE support Piotr Sarna
2019-10-15 10:50 ` Michal Hocko [this message]
2019-10-15 23:37 ` Mike Kravetz
2019-10-21 17:17 ` Mike Kravetz
2019-10-22 7:09 ` Piotr Sarna
2019-10-23 2:55 ` Mike Kravetz
2019-10-23 7:14 ` Piotr Sarna
2019-10-28 18:56 ` Mike Kravetz
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=20191015105055.GA24932@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=p.sarna@tlen.pl \
--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).