From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Rafa?? Mi??ecki <zajec5@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>,
Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
Hans de Goede <hdegoede@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] vboxsf fixes for 5.14-1
Date: Thu, 15 Jul 2021 00:38:00 +0800 [thread overview]
Message-ID: <YO8S6IK8/WsInasF@B-P7TQMD6M-0146.local> (raw)
In-Reply-To: <YO8OP7vzHIuKvO6X@infradead.org>
Hi Christoph,
On Wed, Jul 14, 2021 at 05:18:07PM +0100, Christoph Hellwig wrote:
> On Wed, Jul 14, 2021 at 09:13:52AM -0700, Darrick J. Wong wrote:
> > Porting to fs/iomap can be done after merge, so long as the ntfs3
> > driver doesn't depend on crazy reworking of buffer heads or whatever.
> > AFAICT it didn't, so ... yes, my earlier statements still apply: "later
> > as a clean up".
>
> I on the other hand hate piling up mor of this legacy stuff, as it tends
> to not be cleaned up by the submitted. Example: erofs still hasn't
> switched to iomap despite broad claims, also we still have a huge
Just some word of this, I've been always actively developing and
converting legacy stuffs to new APIs these years, such as new mount
APIs, xarray, which can be seen by changelog compared with other
filesystems. The iomap buffered I/O stuff is mainly because it
doesn't support tailing-packing inline, although which has been
requested for people who cares more about storage itself, like:
https://lore.kernel.org/lkml/3dbeff43-0905-3421-4652-41b7a935f3c1@gmail.com/
And I can also show the benefits by using tailing-packing inline
by taking Linux source code tree (many random tail blocks) as an
example...
I'm now working on this tailing-packing inline iomap support as
well. But Anyway, erofs didn't use buffer head in the beginning
since I can see some flew of buffer head approach itself, it just
works on raw bio and page cache interfaces for now.
Thanks,
Gao Xiang
> backlog in the switch to the new mount API.
next prev parent reply other threads:[~2021-07-14 16:38 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 10:45 [GIT PULL] vboxsf fixes for 5.14-1 Hans de Goede
2021-07-13 19:15 ` Linus Torvalds
2021-07-13 20:14 ` Al Viro
2021-07-13 20:18 ` Al Viro
2021-07-13 20:24 ` Randy Dunlap
2021-07-13 20:32 ` Al Viro
2021-07-13 21:43 ` Randy Dunlap
2021-07-14 10:50 ` Rafał Miłecki
2021-07-14 14:13 ` Christoph Hellwig
2021-07-14 14:51 ` Greg KH
2021-07-14 15:59 ` Rafał Miłecki
2021-07-14 16:05 ` Matthew Wilcox
2021-07-14 16:18 ` Rafał Miłecki
2021-07-15 21:50 ` Neal Gompa
2021-07-16 11:46 ` Leonidas P. Papadakos
2021-07-16 18:07 ` Linus Torvalds
2021-07-30 15:55 ` Konstantin Komarov
2021-07-30 17:23 ` Paragon NTFSv3 (was Re: [GIT PULL] vboxsf fixes for 5.14-1) Linus Torvalds
2021-08-13 16:11 ` Konstantin Komarov
2021-08-15 20:32 ` Stephen Rothwell
2021-08-16 3:00 ` Kari Argillander
2021-09-02 21:55 ` Linus Torvalds
2021-08-03 22:48 ` [GIT PULL] vboxsf fixes for 5.14-1 Theodore Ts'o
2021-08-03 23:44 ` Matthew Wilcox
2021-08-04 0:04 ` Theodore Ts'o
2021-08-04 0:10 ` Linus Torvalds
2021-08-04 0:49 ` Theodore Ts'o
2021-08-04 1:03 ` Darrick J. Wong
2021-08-04 6:38 ` Kari Argillander
2021-08-04 16:30 ` Theodore Ts'o
2021-08-05 15:48 ` Konstantin Komarov
2021-08-10 7:02 ` Darrick J. Wong
2021-09-02 22:09 ` NTFS testing (was: " Szabolcs Szakacsits
2021-09-03 17:48 ` Eric Biggers
2021-09-03 21:17 ` Szabolcs Szakacsits
2021-07-17 16:47 ` Pali Rohár
2021-07-14 16:13 ` Darrick J. Wong
2021-07-14 16:18 ` Christoph Hellwig
2021-07-14 16:38 ` Gao Xiang [this message]
2021-07-14 20:03 ` Eric W. Biederman
2021-07-15 22:14 ` Darrick J. Wong
2021-07-13 19:17 ` pr-tracker-bot
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=YO8S6IK8/WsInasF@B-P7TQMD6M-0146.local \
--to=hsiangkao@linux.alibaba.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=djwong@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=hdegoede@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=zajec5@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;
as well as URLs for NNTP newsgroup(s).