From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Sai Chaitanya Mitta <mittachaitu@gmail.com>, linux-xfs@vger.kernel.org
Subject: Re: Approach to quickly zeroing large XFS file (or) tool to mark XFS file extents as written
Date: Tue, 7 Jan 2025 14:11:21 -0800 [thread overview]
Message-ID: <20250107221121.GK6174@frogsfrogsfrogs> (raw)
In-Reply-To: <Z3znwD53VIBdrlbL@infradead.org>
On Tue, Jan 07, 2025 at 12:37:20AM -0800, Christoph Hellwig wrote:
> On Mon, Jan 06, 2025 at 11:04:59PM -0800, Darrick J. Wong wrote:
> > I get this funny feeling that a lot of programs might like to lease
> > space and get told by the kernel when someone wants/took it back.
> > Swapfiles and lilo ftw.
>
> Well, for swapfiles we can't really take them back. Similarly the lilo
> model is just broken as any chance of the mapping would actually require
> re-installing the boot load in the boot block pointing to the blocks.
I bet the rdma users might like a lease that can't be taken back. We
/did/ talk a hojillion years ago at LSFMM about having a type of lease
that expires when someone tries to change the file; and a different type
of lease that can't expire but causes file operations to error out.
OTOH it's not like I've ever tried to solve this problem. :P
--D
next prev parent reply other threads:[~2025-01-07 22:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 16:42 Approach to quickly zeroing large XFS file (or) tool to mark XFS file extents as written Sai Chaitanya Mitta
2024-12-23 21:53 ` Darrick J. Wong
2024-12-24 5:47 ` Sai Chaitanya Mitta
2025-01-06 19:46 ` Darrick J. Wong
2025-01-07 6:14 ` Christoph Hellwig
2025-01-07 7:04 ` Darrick J. Wong
2025-01-07 8:37 ` Christoph Hellwig
2025-01-07 22:11 ` Darrick J. Wong [this message]
2024-12-24 3:42 ` Dave Chinner
2025-01-06 11:15 ` Christoph Hellwig
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=20250107221121.GK6174@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mittachaitu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.