From: Richard Weinberger <richard.weinberger@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Boris Brezillon <boris.brezillon@collabora.com>,
rminnich@google.com, sven@narfation.org,
LKML <linux-kernel@vger.kernel.org>,
linux-mtd@lists.infradead.org,
"open list:FUSE: FILESYSTEM..."
<fuse-devel@lists.sourceforge.net>
Subject: Re: [PATCH 0/8] MUSE: Userspace backed MTD v3
Date: Mon, 1 Feb 2021 14:14:01 +0100 [thread overview]
Message-ID: <CAFLxGvzQo9H8h5XpLuVDYC8uaRrPmkH444yFv3jX0LNCs_nTmg@mail.gmail.com> (raw)
In-Reply-To: <20210124232007.21639-1-richard@nod.at>
*friendly FUSE maintainer ping* :-)
On Mon, Jan 25, 2021 at 12:24 AM Richard Weinberger <richard@nod.at> wrote:
>
> I'm happy to announce the first non-RFC version of this patch set.
> Over the xmas holidays I found some time to experiment with various userspace
> implementations of MTDs and gave the kernel side more fine-tuning.
>
> Rationale:
> ----------
>
> When working with flash devices a common task is emulating them to run various
> tests or inspect dumps from real hardware. To achieve that we have plenty of
> emulators in the MTD subsystem: mtdram, block2mtd, nandsim.
>
> Each of them implements an ad-hoc MTD and have various drawbacks.
> Over the last years some developers tried to extend them but these attempts
> often got rejected because they added just more adhoc feature instead of
> addressing overall problems.
>
> MUSE is a novel approach to address the need of advanced MTD emulators.
> Advanced means in this context supporting different (vendor specific) image
> formats, different ways for fault injection (fuzzing) and recoding/replaying
> IOs to emulate power cuts.
>
> The core goal of MUSE is having the complexity on the userspace side and
> only a small MTD driver in kernelspace.
> While playing with different approaches I realized that FUSE offers everything
> we need. So MUSE is a little like CUSE except that it does not implement a
> bare character device but an MTD.
>
> Notes:
> ------
>
> - OOB support is currently limited. Currently MUSE has no support for processing
> in- and out-band in the same MTD operation. It is good enough to make JFFS2
> happy. This limitation is because FUSE has no support more than one variable
> length buffer in a FUSE request.
> At least I didn’t find a good way to pass more than one buffer to a request.
> Maybe FUSE folks can correct me. :-)
>
> - Every MTD read/write operation maps 1:1 to a MUSE_READ/WRITE opcode.
> Since FUSE requests are not cheap, the amount of read/written bytes in a MTD
> operation as a huge impact on the performance. Especially when NOR style MTDs
> are implemented in userspace a large writebufsize should be requested to gain
> good write performance.
> On the other hand, MTD operations with lengths larger than writesize are *not*
> split up into multiple MUSE_READ/WRITE requests. This means that userspace
> has to split them manually when doing power-cut emulation.
>
> - MUSE is not super fast. On my i5 workstation nandsim is almost twice as fast
> as a NAND flash in userspace. But MUSE is still magnitudes faster than any
> real world MTD out there. So it is good enough for the use cases I have in
> mind.
>
> Changelog:
> ----------
>
> Changes since v2 (RFC):
> - OOB support
> - MUSE_READ/WRITE opcodes are no longer a min IO MTD unit
> - MTD partitions support via mtdparts string
> - More code cleanup
> - Code rebased to 5.11-rc4
>
> Changes since v1 (RFC):
> - Rewrote IO path, fuse_direct_io() is no longer used.
> Instead of cheating fuse_direct_io() use custom ops to implement
> reading and writing. That way MUSE no longer needs a dummy file object
> nor a fuse file object.
> In MTD all IO is synchronous and operations on kernel buffers, this
> makes IO processing simple for MUSE.
> - Support for bad blocks.
> - No more (ab)use of FUSE ops such as FUSE_FSYNC.
> - Major code cleanup.
>
> This series can also be found at:
> git://git.kernel.org/pub/scm/linux/kernel/git/rw/misc.git muse_v3
>
> Richard Weinberger (8):
> fuse: Export fuse_simple_request
> fuse: Export IO helpers
> fuse: Make cuse_parse_one a common helper
> mtd: Add MTD_MUSE flag
> mtd: Allow passing a custom cmdline to cmdline line parser
> fuse: Add MUSE specific defines FUSE interface
> fuse: Implement MUSE - MTD in userspace
> MAINTAINERS: Add entry for MUSE
>
> Documentation/ABI/testing/sysfs-class-mtd | 8 +
> MAINTAINERS | 7 +
> drivers/mtd/parsers/cmdlinepart.c | 73 +-
> fs/fuse/Kconfig | 15 +
> fs/fuse/Makefile | 2 +
> fs/fuse/cuse.c | 58 +-
> fs/fuse/dev.c | 1 +
> fs/fuse/file.c | 16 +-
> fs/fuse/fuse_i.h | 18 +
> fs/fuse/helper.c | 70 ++
> fs/fuse/muse.c | 1086 +++++++++++++++++++++
> include/linux/mtd/partitions.h | 2 +
> include/uapi/linux/fuse.h | 76 ++
> include/uapi/mtd/mtd-abi.h | 1 +
> 14 files changed, 1346 insertions(+), 87 deletions(-)
> create mode 100644 fs/fuse/helper.c
> create mode 100644 fs/fuse/muse.c
>
> --
> 2.26.2
>
--
Thanks,
//richard
next prev parent reply other threads:[~2021-02-01 13:15 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 23:19 [PATCH 0/8] MUSE: Userspace backed MTD v3 Richard Weinberger
2021-01-24 23:20 ` [PATCH 1/8] fuse: Export fuse_simple_request Richard Weinberger
2021-01-24 23:20 ` [PATCH 2/8] fuse: Export IO helpers Richard Weinberger
2021-01-24 23:20 ` [PATCH 3/8] fuse: Make cuse_parse_one a common helper Richard Weinberger
2021-01-24 23:20 ` [PATCH 4/8] mtd: Add MTD_MUSE flag Richard Weinberger
2021-01-24 23:20 ` [PATCH 5/8] mtd: Allow passing a custom cmdline to cmdline line parser Richard Weinberger
2021-01-24 23:20 ` [PATCH 6/8] fuse: Add MUSE specific defines FUSE interface Richard Weinberger
2021-01-24 23:20 ` [PATCH 7/8] fuse: Implement MUSE - MTD in userspace Richard Weinberger
2021-01-24 23:20 ` [PATCH 8/8] MAINTAINERS: Add entry for MUSE Richard Weinberger
2021-01-28 10:30 ` [PATCH 0/8] MUSE: Userspace backed MTD v3 Miquel Raynal
2021-02-01 13:14 ` Richard Weinberger [this message]
2021-02-01 13:55 ` Miklos Szeredi
2021-02-09 14:26 ` Miklos Szeredi
2021-02-09 14:35 ` Richard Weinberger
2021-02-09 15:10 ` [fuse-devel] " Luca Risolia
2021-02-09 15:22 ` Miklos Szeredi
2021-02-09 15:41 ` Richard Weinberger
2021-02-09 15:56 ` Luca Risolia
2021-02-09 16:04 ` Richard Weinberger
2021-02-09 16:28 ` Luca Risolia
2021-02-09 16:29 ` Richard Weinberger
2021-02-09 16:42 ` Luca Risolia
2021-02-09 16:50 ` Richard Weinberger
2021-02-09 17:46 ` Luca Risolia
2021-02-09 19:42 ` Miklos Szeredi
2021-02-09 20:06 ` Richard Weinberger
2021-02-10 10:12 ` Miklos Szeredi
2021-02-10 11:12 ` Richard Weinberger
2021-02-10 11:16 ` Miklos Szeredi
2021-02-11 18:09 ` Miklos Szeredi
2021-04-13 12:59 ` Miklos Szeredi
2021-02-09 21:39 ` Richard Weinberger
2021-02-10 10:16 ` Miklos Szeredi
2021-02-10 11:00 ` Richard Weinberger
2021-02-10 11:14 ` Miquel Raynal
2021-02-10 11:23 ` Richard Weinberger
2021-02-10 20:55 ` Miquel Raynal
2021-02-10 21:11 ` Richard Weinberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFLxGvzQo9H8h5XpLuVDYC8uaRrPmkH444yFv3jX0LNCs_nTmg@mail.gmail.com \
--to=richard.weinberger@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miklos@szeredi.hu \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=rminnich@google.com \
--cc=sven@narfation.org \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).