mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Artem S. Tashkinov" <aros@gmx.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Spooling large metadata updates / Proposal for a new API/feature in the Linux Kernel (VFS/Filesystems):
Date: Sat, 11 Jan 2025 09:17:49 +0000	[thread overview]
Message-ID: <ba4f3df5-027b-405e-8e6e-a3630f7eef93@gmx.com> (raw)

Hello,

I had this idea on 2021-11-07, then I thought it was wrong/stupid, now
I've asked AI and it said it was actually not bad, so I'm bringing it
forward now:

Imagine the following scenarios:

  * You need to delete tens of thousands of files.
  * You need to change the permissions, ownership, or security context
(chmod, chown, chcon) for tens of thousands of files.
  * You need to update timestamps for tens of thousands of files.

All these operations are currently relatively slow because they are
executed sequentially, generating significant I/O overhead.

What if these operations could be spooled and performed as a single
transaction? By bundling metadata updates into one atomic operation,
such tasks could become near-instant or significantly faster. This would
also reduce the number of writes, leading to less wear and tear on
storage devices.

Does this idea make sense? If it already exists, or if there’s a reason
it wouldn’t work, please let me know.


Best regards,
Artem

             reply	other threads:[~2025-01-11  9:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-11  9:17 Artem S. Tashkinov [this message]
2025-01-11 10:33 ` Amir Goldstein
2025-01-12  5:27 ` Theodore Ts'o
2025-01-12 11:58   ` Matthew Wilcox
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=ba4f3df5-027b-405e-8e6e-a3630f7eef93@gmx.com \
    --to=aros@gmx.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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®