From: Matthew Wilcox <willy@infradead.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: "Artem S. Tashkinov" <aros@gmx.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Spooling large metadata updates / Proposal for a new API/feature in the Linux Kernel (VFS/Filesystems):
Date: Sun, 12 Jan 2025 11:58:53 +0000 [thread overview]
Message-ID: <Z4OufXVYupmI8yuN@casper.infradead.org> (raw)
In-Reply-To: <20250112052743.GH1323402@mit.edu>
On Sun, Jan 12, 2025 at 12:27:43AM -0500, Theodore Ts'o wrote:
> So yes, it basically exists, although in practice, it doesn't work as
> well as you might think, because of the need to read potentially a
> large number of the metdata blocks. But for example, if you make sure
> that all of the inode information is already cached, e.g.:
>
> ls -lR /path/to/large/tree > /dev/null
>
> Then the operation to do a bulk update will be fast:
>
> time chown -R root:root /path/to/large/tree
>
> This demonstrates that the bottleneck tends to be *reading* the
> metdata blocks, not *writing* the metadata blocks.
So if we presented more of the operations to the kernel at once, it
could pipeline the reading of the metadata, providing a user-visible
win.
However, I don't know that we need a new user API to do it. This is
something that could be done in the "rm" tool; it has the information
it needs, and it's better to put heuristics like "how far to read ahead"
in userspace than the kernel.
next prev parent reply other threads:[~2025-01-12 11:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-11 9:17 Artem S. Tashkinov
2025-01-11 10:33 ` Amir Goldstein
2025-01-12 5:27 ` Theodore Ts'o
2025-01-12 11:58 ` Matthew Wilcox [this message]
2025-01-12 18:12 ` Darrick J. Wong
2025-01-13 7:41 ` Artem S. Tashkinov
2025-01-13 14:00 ` Theodore Ts'o
2025-01-13 23:31 ` Dave Chinner
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=Z4OufXVYupmI8yuN@casper.infradead.org \
--to=willy@infradead.org \
--cc=aros@gmx.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®