[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1507208626.379155.1612906761549.JavaMail.zimbra@nod.at>
Date: Tue, 9 Feb 2021 22:39:21 +0100 (CET)
From: Richard Weinberger <richard@....at>
To: Miklos Szeredi <miklos@...redi.hu>
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
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.
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?
Thanks,
//richard
Powered by blists - more mailing lists