Re: [PATCH V11 0/9] famfs: port into fuse
Miklos Szeredi <[email protected]> Sat, 25 Jul 2026 06:01:30 +0200
| Newsgroups | dev.linux.lists.fuse-devel,dev.linux.lists.nvdimm,org.kernel.vger.linux-cxl,org.kernel.vger.linux-doc,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <CAJfpeguEptz4sEXq=pBWPFop--1kTDu5p2yZnCyzXcrZ28Nekw@mail.gmail.com> |
(Replying shortly as we are starting now on a two week journey. Won't read email during this time). On Fri, 24 Jul 2026 at 22:23, Joanne Koong <[email protected]> wrote: > imo these changes seem doable for making the 7.3 merge window. I'm not > sure how much bandwidth John has though. Maybe one idea that could > work if John is completely slammed for time right now is having the > changes requested above be a separate followup series someone else can > do and then this current series (after the sashiko fixes) and that > series can get landed together in the same merge window. I'm all for it. > > > > > Maybe the striping setup can also be done with a notification. The > > I had interpreted the FUSE_DEV_IOC_STRIPE_OPEN patch as implying that > the mapping gets forwarded to the kernel through the backing id in the > open() reply, which I think is how Amir had also interpreted it. I > didn't like that the striping mappings got sent through an ioctl while > the simple mappings didn't, but I think maybe the patch was not trying > to suggest that and I had interpreted it too literally. I like the > striping setup through an ioctl - I think it makes sense given that it > is connection-level instead of inode-level. Yeah, the striping setup is on a different level (like we have with regular filesystems). So I think it's not that bad that the setup is different. Thanks, Miklos