From: "Richard W.M. Jones" <rjones@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Teng-Feng Yang <shinrairis@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] TRIM/DISCARD/UNMAP support on qemu-nbd
Date: Tue, 7 Jan 2014 21:22:10 +0000 [thread overview]
Message-ID: <20140107212210.GB4802@redhat.com> (raw)
In-Reply-To: <52CC6811.4000107@redhat.com>
On Tue, Jan 07, 2014 at 09:48:17PM +0100, Paolo Bonzini wrote:
> Il 07/01/2014 21:27, Richard W.M. Jones ha scritto:
> > Not much more what I said in the original email (especially see the
> > attached script which you can download from the bottom of this page:
> > https://lists.gnu.org/archive/html/qemu-devel/2014-01/msg00084.html )
> >
> > Basically it tries to dd /dev/zero into the virtio-scsi device exposed
> > by qemu, then calls sg_unmap (there are two devices, it only unmaps
> > the first so we can hopefully see the difference), but it doesn't seem
> > to have any effect on the underlying file. The underlying file is a
> > regular raw-format file on ext4.
> >
> > I called sg_readcap/sg_vpd and we seem to have all the right
> > capability bits exposed.
> >
> > This script won't work with regular libguestfs. I compiled a special
> > appliance that had the sg tools included.
>
> Try again with the pull request of
> http://permalink.gmane.org/gmane.comp.emulators.qemu/248421
No difference from before, as far as I can see.
Here is the output of sparsetest.sh:
0 /tmp/test1
0 /tmp/test2
Read Capacity results:
Protection: prot_en=0, p_type=0, p_i_exponent=0
Logical block provisioning: lbpme=1, lbprz=0
Last logical block address=204799 (0x31fff), Number of logical blocks=204800
Logical block length=512 bytes
Logical blocks per physical block exponent=0
Lowest aligned logical block address=0
Hence:
Device size: 104857600 bytes, 100.0 MiB, 0.10 GB
Block limits VPD page (SBC):
Write same no zero (WSNZ): 1
Maximum compare and write length: 0 blocks
Optimal transfer length granularity: 0 blocks
Maximum transfer length: 0 blocks
Optimal transfer length: 0 blocks
Maximum prefetch length: 0 blocks
Maximum unmap LBA count: 2097152
Maximum unmap block descriptor count: 255
Optimal unmap granularity: 8
Unmap granularity alignment valid: 0
Unmap granularity alignment: 0
Maximum write same length: 0x0 blocks
16M /tmp/test1 <--- note both file disk
16M /tmp/test2 <--- usages are the same
Those are raw files on ext4. I'll try qcow2 and follow up.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
next prev parent reply other threads:[~2014-01-07 21:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 11:58 [Qemu-devel] TRIM/DISCARD/UNMAP support on qemu-nbd Teng-Feng Yang
2014-01-02 16:15 ` Richard W.M. Jones
2014-01-07 14:48 ` Paolo Bonzini
2014-01-07 20:27 ` Richard W.M. Jones
2014-01-07 20:48 ` Paolo Bonzini
2014-01-07 21:22 ` Richard W.M. Jones [this message]
2014-01-08 22:11 ` Paolo Bonzini
2014-01-08 22:24 ` Richard W.M. Jones
2014-01-08 22:45 ` Paolo Bonzini
2014-01-08 22:53 ` Richard W.M. Jones
2014-01-09 7:02 ` Paolo Bonzini
2014-01-07 21:27 ` Richard W.M. Jones
2014-01-06 2:45 ` Stefan Hajnoczi
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=20140107212210.GB4802@redhat.com \
--to=rjones@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shinrairis@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.