From: Matthew Wilcox <willy@infradead.org>
To: Cong Wang <cwang@multikernel.io>
Cc: Gao Xiang <hsiangkao@linux.alibaba.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Cong Wang <xiyou.wangcong@gmail.com>,
multikernel@lists.linux.dev
Subject: Re: [ANNOUNCE] DAXFS: A zero-copy, dmabuf-friendly filesystem for shared memory
Date: Mon, 26 Jan 2026 19:16:46 +0000 [thread overview]
Message-ID: <aXe9nhAsK2lzOoxY@casper.infradead.org> (raw)
In-Reply-To: <CAGHCLaQbr2Q1KwEJhsZGuaFV=m6WEkxsgurg30+pjSQ4dHQ_1Q@mail.gmail.com>
On Mon, Jan 26, 2026 at 09:38:23AM -0800, Cong Wang wrote:
> If you are interested in adding multikernel support to EROFS, here is
> the codebase you could start with:
> https://github.com/multikernel/linux. PR is always welcome.
I think the onus is rather the other way around. Adding a new filesystem
to Linux has a high bar to clear because it becomes a maintenance burden
to the rest of us. Convince us that what you're doing here *can't*
be done better by modifying erofs.
Before I saw the email from Gao Xiang, I was also going to suggest that
using erofs would be a better idea than supporting your own filesystem.
Writing a new filesystem is a lot of fun. Supporting a new filesystem
and making it production-quality is a whole lot of pain. It's much
better if you can leverage other people's work. That's why DAX is a
support layer for filesystems rather than its own filesystem.
next prev parent reply other threads:[~2026-01-26 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGHCLaREA4xzP7CkJrpqu4C=PKw_3GppOUPWZKn0Fxom_3Z9Qw@mail.gmail.com>
[not found] ` <55e3d9f6-50d2-48c0-b7e3-fb1c144cf3e8@linux.alibaba.com>
2026-01-26 17:38 ` [ANNOUNCE] DAXFS: A zero-copy, dmabuf-friendly filesystem for shared memory Cong Wang
2026-01-26 19:16 ` Matthew Wilcox [this message]
2026-01-26 19:48 ` Cong Wang
2026-01-26 20:13 ` Gao Xiang
2026-01-26 20:40 ` Matthew Wilcox
2026-01-27 0:02 ` Cong Wang
2026-01-27 0:55 ` Gao Xiang
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=aXe9nhAsK2lzOoxY@casper.infradead.org \
--to=willy@infradead.org \
--cc=cwang@multikernel.io \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=multikernel@lists.linux.dev \
--cc=xiyou.wangcong@gmail.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