[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJfpegugbvppOKhJ8KjSVGgZOGVuj6NSiy4n18mbD7Ui3wme6g@mail.gmail.com>
Date: Wed, 10 Feb 2021 11:16:45 +0100
From: Miklos Szeredi <miklos@...redi.hu>
To: Richard Weinberger <richard@....at>
Cc: Miquel Raynal <miquel.raynal@...tlin.com>,
Vignesh Raghavendra <vigneshr@...com>,
Boris Brezillon <boris.brezillon@...labora.com>,
Ron Minnich <rminnich@...gle.com>, sven <sven@...fation.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-mtd <linux-mtd@...ts.infradead.org>,
fuse-devel <fuse-devel@...ts.sourceforge.net>
Subject: Re: [PATCH 0/8] MUSE: Userspace backed MTD v3
On Tue, Feb 9, 2021 at 10:39 PM Richard Weinberger <richard@....at> wrote:
>
> Miklos,
>
> ----- Ursprüngliche Mail -----
> > If you look at fuse_do_ioctl() it does variable length input and
> > output at the same time. I guess you need something similar to that.
>
> I'm not sure whether I understand correctly.
>
> In MUSE one use case would be attaching two distinct (variable length) buffers to a
> single FUSE request, in both directions.
> If I read fuse_do_ioctl() correctly, it attaches always a single buffer per request
> but does multiple requests.
Right.
> In MUSE we cold go the same path and issue up to two requests.
> One for in-band and optionally a second one for the out-of-band data.
> Hmmm?
Does in-band and OOB data need to be handled together? If so, then
two requests is not a good option.
Thanks,
Miklos
Powered by blists - more mailing lists