From: Peter Lieven <pl@kamp.de>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com, Peter Lieven <pl@kamp.de>,
ronniesahlberg@gmail.com, stefanha@redhat.com
Subject: [Qemu-devel] [PATCHv5 0/3] iscsi/qemu-img/block-migration enhancements
Date: Fri, 19 Jul 2013 09:19:38 +0200 [thread overview]
Message-ID: <1374218381-18597-1-git-send-email-pl@kamp.de> (raw)
this series adds logical block provisioning functions to the iscsi layer.
it also is the first step to the change of migration to coroutines in
block/iscsi.
v4->v5:
- rebased to master + stefanha/block
- patch1: fetching block limits page also if lbpws == 1
- patch2: converted to get block status api
- moved iscsi_co_init_iscsitask up to avoid memory corruption
if we go out in an early error case
- added alignment check
- added max_unmap limit here if max_unmap == 0xffffffff
- patch3: - readded because we agreed not to touch bdrv_discard after all
- added alignment check
- silently fail in case of a check condition
Peter Lieven (3):
iscsi: add logical block provisioning information to iscsilun
iscsi: add .bdrv_get_block_status
iscsi: add .bdrv_co_discard
block/iscsi.c | 368 ++++++++++++++++++++++++++++++++++++++++++++-------------
1 file changed, 285 insertions(+), 83 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-07-19 7:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 7:19 Peter Lieven [this message]
2013-07-19 7:19 ` [Qemu-devel] [PATCHv5 1/3] iscsi: add logical block provisioning information to iscsilun Peter Lieven
2013-07-19 7:19 ` [Qemu-devel] [PATCHv5 2/3] iscsi: add .bdrv_get_block_status Peter Lieven
2013-07-19 7:19 ` [Qemu-devel] [PATCHv5 3/3] iscsi: add .bdrv_co_discard Peter Lieven
2013-07-19 9:18 ` Paolo Bonzini
2013-07-19 9:37 ` Peter Lieven
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=1374218381-18597-1-git-send-email-pl@kamp.de \
--to=pl@kamp.de \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
--cc=stefanha@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).