Linux-Fsdevel Archive on lore.kernel.org help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu> To: Vivek Goyal <vgoyal@redhat.com> Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-nvdimm <linux-nvdimm@lists.01.org>, virtio-fs-list <virtio-fs@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>, "Dr. David Alan Gilbert" <dgilbert@redhat.com>, Dan Williams <dan.j.williams@intel.com> Subject: Re: [PATCH v3 11/18] fuse: implement FUSE_INIT map_alignment field Date: Wed, 26 Aug 2020 16:06:35 +0200 [thread overview] Message-ID: <CAJfpegsgHE0MkZLFgE4yrZXO5ThDxCj85-PjizrXPRC2CceT1g@mail.gmail.com> (raw) In-Reply-To: <20200819221956.845195-12-vgoyal@redhat.com> On Thu, Aug 20, 2020 at 12:21 AM Vivek Goyal <vgoyal@redhat.com> wrote: > > The device communicates FUSE_SETUPMAPPING/FUSE_REMOVMAPPING alignment > constraints via the FUST_INIT map_alignment field. Parse this field and > ensure our DAX mappings meet the alignment constraints. > > We don't actually align anything differently since our mappings are > already 2MB aligned. Just check the value when the connection is > established. If it becomes necessary to honor arbitrary alignments in > the future we'll have to adjust how mappings are sized. > > The upshot of this commit is that we can be confident that mappings will > work even when emulating x86 on Power and similar combinations where the > host page sizes are different. > > Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> > Signed-off-by: Vivek Goyal <vgoyal@redhat.com> > --- > fs/fuse/fuse_i.h | 5 ++++- > fs/fuse/inode.c | 18 ++++++++++++++++-- > include/uapi/linux/fuse.h | 4 +++- > 3 files changed, 23 insertions(+), 4 deletions(-) > > diff --git a/fs/fuse/fuse_i.h b/fs/fuse/fuse_i.h > index 478c940b05b4..4a46e35222c7 100644 > --- a/fs/fuse/fuse_i.h > +++ b/fs/fuse/fuse_i.h > @@ -47,7 +47,10 @@ > /** Number of dentries for each connection in the control filesystem */ > #define FUSE_CTL_NUM_DENTRIES 5 > > -/* Default memory range size, 2MB */ > +/* > + * Default memory range size. A power of 2 so it agrees with common FUSE_INIT > + * map_alignment values 4KB and 64KB. > + */ > #define FUSE_DAX_SZ (2*1024*1024) > #define FUSE_DAX_SHIFT (21) > #define FUSE_DAX_PAGES (FUSE_DAX_SZ/PAGE_SIZE) > diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c > index b82eb61d63cc..947abdd776ca 100644 > --- a/fs/fuse/inode.c > +++ b/fs/fuse/inode.c > @@ -980,9 +980,10 @@ static void process_init_reply(struct fuse_conn *fc, struct fuse_args *args, > { > struct fuse_init_args *ia = container_of(args, typeof(*ia), args); > struct fuse_init_out *arg = &ia->out; > + bool ok = true; > > if (error || arg->major != FUSE_KERNEL_VERSION) > - fc->conn_error = 1; > + ok = false; > else { > unsigned long ra_pages; > > @@ -1045,6 +1046,13 @@ static void process_init_reply(struct fuse_conn *fc, struct fuse_args *args, > min_t(unsigned int, FUSE_MAX_MAX_PAGES, > max_t(unsigned int, arg->max_pages, 1)); > } > + if ((arg->flags & FUSE_MAP_ALIGNMENT) && > + (FUSE_DAX_SZ % (1ul << arg->map_alignment))) { This just obfuscates "arg->map_alignment != FUSE_DAX_SHIFT". So the intention was that userspace can ask the kernel for a particular alignment, right? In that case kernel can definitely succeed if the requested alignment is smaller than the kernel provided one, no? It would also make sense to make this a two way negotiation. I.e. send the largest alignment (FUSE_DAX_SHIFT in this implementation) that the kernel can provide in fuse_init_in. In that case the only error would be if userspace ignored the given constraints. Am I getting not getting something? > + pr_err("FUSE: map_alignment %u incompatible" > + " with dax mem range size %u\n", > + arg->map_alignment, FUSE_DAX_SZ); > + ok = false; > + } > } else { > ra_pages = fc->max_read / PAGE_SIZE; > fc->no_lock = 1; > @@ -1060,6 +1068,11 @@ static void process_init_reply(struct fuse_conn *fc, struct fuse_args *args, > } > kfree(ia); > > + if (!ok) { > + fc->conn_init = 0; > + fc->conn_error = 1; > + } > + > fuse_set_initialized(fc); > wake_up_all(&fc->blocked_waitq); > } > @@ -1082,7 +1095,8 @@ void fuse_send_init(struct fuse_conn *fc) > FUSE_WRITEBACK_CACHE | FUSE_NO_OPEN_SUPPORT | > FUSE_PARALLEL_DIROPS | FUSE_HANDLE_KILLPRIV | FUSE_POSIX_ACL | > FUSE_ABORT_ERROR | FUSE_MAX_PAGES | FUSE_CACHE_SYMLINKS | > - FUSE_NO_OPENDIR_SUPPORT | FUSE_EXPLICIT_INVAL_DATA; > + FUSE_NO_OPENDIR_SUPPORT | FUSE_EXPLICIT_INVAL_DATA | > + FUSE_MAP_ALIGNMENT; > ia->args.opcode = FUSE_INIT; > ia->args.in_numargs = 1; > ia->args.in_args[0].size = sizeof(ia->in); > diff --git a/include/uapi/linux/fuse.h b/include/uapi/linux/fuse.h > index 373cada89815..5b85819e045f 100644 > --- a/include/uapi/linux/fuse.h > +++ b/include/uapi/linux/fuse.h > @@ -313,7 +313,9 @@ struct fuse_file_lock { > * FUSE_CACHE_SYMLINKS: cache READLINK responses > * FUSE_NO_OPENDIR_SUPPORT: kernel supports zero-message opendir > * FUSE_EXPLICIT_INVAL_DATA: only invalidate cached pages on explicit request > - * FUSE_MAP_ALIGNMENT: map_alignment field is valid > + * FUSE_MAP_ALIGNMENT: init_out.map_alignment contains log2(byte alignment) for > + * foffset and moffset fields in struct > + * fuse_setupmapping_out and fuse_removemapping_one. fuse_setupmapping_in Thanks, Miklos
next prev parent reply other threads:[~2020-08-26 14:07 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-19 22:19 [PATCH v3 00/18] virtiofs: Add DAX support Vivek Goyal 2020-08-19 22:19 ` [PATCH v3 01/18] dax: Modify bdev_dax_pgoff() to handle NULL bdev Vivek Goyal 2020-08-19 22:19 ` [PATCH v3 02/18] dax: Create a range version of dax_layout_busy_page() Vivek Goyal 2020-08-20 12:58 ` Jan Kara 2020-08-20 14:29 ` Vivek Goyal 2020-08-19 22:19 ` [PATCH v3 03/18] virtio: Add get_shm_region method Vivek Goyal 2020-08-19 22:19 ` [PATCH v3 04/18] virtio: Implement get_shm_region for PCI transport Vivek Goyal 2020-08-19 22:19 ` [PATCH v3 05/18] virtio: Implement get_shm_region for MMIO transport Vivek Goyal 2020-08-19 22:19 ` [PATCH v3 06/18] virtiofs: Provide a helper function for virtqueue initialization Vivek Goyal 2020-08-19 22:19 ` [PATCH v3 07/18] fuse: Get rid of no_mount_options Vivek Goyal 2020-08-19 22:19 ` [PATCH v3 08/18] virtio_fs, dax: Set up virtio_fs dax_device Vivek Goyal 2020-08-19 22:19 ` [PATCH v3 09/18] fuse,virtiofs: Add a mount option to enable dax Vivek Goyal 2020-08-19 22:19 ` [PATCH v3 10/18] fuse,virtiofs: Keep a list of free dax memory ranges Vivek Goyal 2020-08-19 22:19 ` [PATCH v3 11/18] fuse: implement FUSE_INIT map_alignment field Vivek Goyal 2020-08-26 14:06 ` Miklos Szeredi [this message] 2020-08-26 15:51 ` Vivek Goyal 2020-08-26 17:34 ` Stefan Hajnoczi 2020-08-26 19:17 ` Dr. David Alan Gilbert 2020-08-26 19:26 ` Miklos Szeredi 2020-08-26 19:53 ` Vivek Goyal 2020-08-19 22:19 ` [PATCH v3 12/18] fuse: Introduce setupmapping/removemapping commands Vivek Goyal 2020-08-19 22:19 ` [PATCH v3 13/18] fuse, dax: Implement dax read/write operations Vivek Goyal 2020-08-19 22:19 ` [PATCH v3 14/18] fuse,dax: add DAX mmap support Vivek Goyal 2020-08-19 22:19 ` [PATCH v3 15/18] fuse,virtiofs: Define dax address space operations Vivek Goyal 2020-08-19 22:19 ` [PATCH v3 16/18] fuse, dax: Serialize truncate/punch_hole and dax fault path Vivek Goyal 2020-08-19 22:19 ` [PATCH v3 17/18] fuse,virtiofs: Maintain a list of busy elements Vivek Goyal 2020-08-19 22:19 ` [PATCH v3 18/18] fuse,virtiofs: Add logic to free up a memory range Vivek Goyal 2020-08-28 14:26 ` [PATCH v3 00/18] virtiofs: Add DAX support Miklos Szeredi 2020-08-28 14:39 ` Vivek Goyal
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=CAJfpegsgHE0MkZLFgE4yrZXO5ThDxCj85-PjizrXPRC2CceT1g@mail.gmail.com \ --to=miklos@szeredi.hu \ --cc=dan.j.williams@intel.com \ --cc=dgilbert@redhat.com \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-nvdimm@lists.01.org \ --cc=stefanha@redhat.com \ --cc=vgoyal@redhat.com \ --cc=virtio-fs@redhat.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: linkBe 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).