From: Gordan Bobic <gordan@bobich.net>
To: kvm@vger.kernel.org
Subject: Disk Emulation and Trim Instruction
Date: Thu, 13 Aug 2009 23:11:36 +0100 [thread overview]
Message-ID: <4A848F98.8010308@bobich.net> (raw)
With the recent talk of the trim SATA instruction becoming supported in
the upcoming versions of Windows and claims from Intel that support for
it in their SSDs is imminent, it occurs to me that this would be equally
useful in virtual disk emulation.
Since the disk image is a sparse file, it always only grows, and
eventually it will grow to it's full intended size even if the actual
used space is a small fraction of the container size. Since the trim
instruction tells the disk that a particular block is no longer used
(and can thus be scheduled for erasing as and when required), the same
thing could be used to reclaim space used by sparse files backing the
VM. It would allow for higher overcommit of disk usage on VM farms.
Is this feature likely to be available in KVM soon?
Gordan
next reply other threads:[~2009-08-13 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 22:11 Gordan Bobic [this message]
2009-08-16 11:43 ` Disk Emulation and Trim Instruction Avi Kivity
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=4A848F98.8010308@bobich.net \
--to=gordan@bobich.net \
--cc=kvm@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;
as well as URLs for NNTP newsgroup(s).