From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Cc: Luke -Jr <luke@dashjr.org>
Subject: Re: [Qemu-devel] copy on write-but-no-change
Date: Tue, 11 Sep 2007 01:47:16 -0500 [thread overview]
Message-ID: <200709110147.16434.rob@landley.net> (raw)
In-Reply-To: <200709071040.15626.luke@dashjr.org>
On Friday 07 September 2007 10:40:15 am Luke -Jr wrote:
> I don't believe it's possible to make holes in sparse files explicitly.
> The libc/OS only support it transparently when you jump to the end of a
> file and begin writing there.
Actually, I believe it should finally show up in the 2.6.23 kernel. Look for
fadvise(FA_DEALLOCATE)
http://lwn.net/Articles/226710/
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
prev parent reply other threads:[~2007-09-11 6:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 22:55 [Qemu-devel] copy on write-but-no-change Lapo Luchini
2007-09-07 15:40 ` Luke -Jr
2007-09-11 6:47 ` Rob Landley [this message]
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=200709110147.16434.rob@landley.net \
--to=rob@landley.net \
--cc=luke@dashjr.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).