[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFLxGvwhdHeUDR8Mk8kyMvMCcRc4S4pcjs29ttPTHL2XWW93fg@mail.gmail.com>
Date: Wed, 10 Feb 2021 12:00:08 +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:22 AM Miklos Szeredi <miklos@...redi.hu> wrote:
> > 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.
They can be handled separately. All I need to figure who to abstract this nicely
in libfuse.
--
Thanks,
//richard
Powered by blists - more mailing lists