[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFLxGvxhxxfT_ugmeFuqZ099Z+v-ENg9C6zq78sV45YzA5_Y_w@mail.gmail.com>
Date: Wed, 10 Feb 2021 12:12:03 +0100
From: Richard Weinberger <richard.weinberger@...il.com>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
fuse-devel <fuse-devel@...ts.sourceforge.net>,
Miquel Raynal <miquel.raynal@...tlin.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Boris Brezillon <boris.brezillon@...labora.com>,
linux-mtd <linux-mtd@...ts.infradead.org>,
Ron Minnich <rminnich@...gle.com>, sven <sven@...fation.org>
Subject: Re: [PATCH 0/8] MUSE: Userspace backed MTD v3
On Wed, Feb 10, 2021 at 11:18 AM Miklos Szeredi <miklos@...redi.hu> wrote:
> > Does this more or less what you had in mind?
>
> Just moving the whole internal header file is not nice. I did a
> mechanical public/private separation of the interface based on what
> CUSE uses. Incremental patch attached.
>
> But this is just a start. From the big structures still left in
> <net/fuse.h> CUSE only uses the following fields:
>
> fc: .minor, max_read, max_write, rcu, release, initialized, num_waiting
> fm: .fc
> ff: .fm
> fud: .fc
>
> Dealing with the last 3 is trivial: create and alloc function for the
> fm, and create accessor functions for the accessed fields.
Ah, ok. So the goal is that <net/fuse.h> provides the bare minimum such that
CUSE and MUSE can reside outside of fs/fuse?
> Dealing with fc properly is probably a bit more involved, but does not
> seem to be too compex at first glance.
>
> Do you want to take a stab at cleaning this up further?
Yes. I guess for MUSE the interface needs little adaptations as well.
But I won't be able to do this for the 5.12 merge window.
--
Thanks,
//richard
Powered by blists - more mailing lists