From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: kwolf@redhat.com, "Richard W.M. Jones" <rjones@redhat.com>,
Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block: Add -drive detect_zero=on|off option to detect all zero writes.
Date: Mon, 30 Jul 2012 16:09:32 +0200 [thread overview]
Message-ID: <5016959C.5070004@redhat.com> (raw)
In-Reply-To: <5016944B.8070501@redhat.com>
Il 30/07/2012 16:03, Eric Blake ha scritto:
> Ooh, nice bullet point to add to my upcoming presentation at Linux
> Plumber's Conference in a month:
> http://summit.linuxplumbersconf.org/lpc-2012/meeting/33/lpc2012-ref-improved-virt-disk-handling/
>
> Does anyone else have some annoyances about large sparse file handling
> where improving the kernel would make our life easier, that I should
> incorporate into my discussion?
In case you haven't mentioned them:
* lseek(SEEK_HOLE/SEEK_DATA) support in the block layer using GET LBA
STATUS.
* support for connecting to an iSCSI target without scanning partitions.
* support for fsync/fdatasync with ranges (or alternatively,
sync_file_range that writes metadata).
Paolo
next prev parent reply other threads:[~2012-07-30 14:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 15:59 [Qemu-devel] [PATCH] Detect zero writes (for discussion only, not to be applied) Richard W.M. Jones
2012-07-26 15:59 ` [Qemu-devel] [PATCH] block: Add -drive detect_zero=on|off option to detect all zero writes Richard W.M. Jones
2012-07-27 13:58 ` Anthony Liguori
2012-07-27 19:01 ` Paolo Bonzini
2012-07-30 13:51 ` Richard W.M. Jones
2012-07-30 13:57 ` Paolo Bonzini
2012-07-30 14:03 ` Eric Blake
2012-07-30 14:09 ` Paolo Bonzini [this message]
2012-07-30 14:38 ` Kevin Wolf
2012-07-30 15:52 ` Richard W.M. Jones
2012-07-27 13:55 ` [Qemu-devel] [PATCH] Detect zero writes (for discussion only, not to be applied) Anthony Liguori
2012-07-27 15:14 ` Richard W.M. Jones
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=5016959C.5070004@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.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 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).