All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, jsnow@redhat.com,
	mreitz@redhat.com, stefanha@redhat.com, den@openvz.org
Subject: Re: [Qemu-devel] [PATCH 0/9] block: buffer-based io
Date: Tue, 30 Apr 2019 12:52:56 +0200	[thread overview]
Message-ID: <20190430105256.GE5607@linux.fritz.box> (raw)
In-Reply-To: <20190422145838.70903-1-vsementsov@virtuozzo.com>

Am 22.04.2019 um 16:58 hat Vladimir Sementsov-Ogievskiy geschrieben:
> Hi all!
> 
> We often need to do read/write with buffer, not qiov. Instead of
> creating qiov in such cases, let's introduce corresponding helpers.

Thanks, applied to the block branch.

As I wrote in patch 4, a follow-up that adds coroutine_fn markers where
we rely on being in coroutine context now would be nice.

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: Kevin Wolf <kwolf@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org, mreitz@redhat.com,
	stefanha@redhat.com, den@openvz.org, jsnow@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/9] block: buffer-based io
Date: Tue, 30 Apr 2019 12:52:56 +0200	[thread overview]
Message-ID: <20190430105256.GE5607@linux.fritz.box> (raw)
Message-ID: <20190430105256.ngrJ3V8XZ24CLMTehlaubjzkNvmgzTFKvyz7RoHJ0Ko@z> (raw)
In-Reply-To: <20190422145838.70903-1-vsementsov@virtuozzo.com>

Am 22.04.2019 um 16:58 hat Vladimir Sementsov-Ogievskiy geschrieben:
> Hi all!
> 
> We often need to do read/write with buffer, not qiov. Instead of
> creating qiov in such cases, let's introduce corresponding helpers.

Thanks, applied to the block branch.

As I wrote in patch 4, a follow-up that adds coroutine_fn markers where
we rely on being in coroutine context now would be nice.

Kevin


  parent reply	other threads:[~2019-04-30 11:05 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-22 14:58 [Qemu-devel] [PATCH 0/9] block: buffer-based io Vladimir Sementsov-Ogievskiy
2019-04-22 14:58 ` Vladimir Sementsov-Ogievskiy
2019-04-22 14:58 ` [Qemu-devel] [PATCH 1/9] block: introduce byte-based io helpers Vladimir Sementsov-Ogievskiy
2019-04-22 14:58   ` Vladimir Sementsov-Ogievskiy
2019-04-22 14:58 ` [Qemu-devel] [PATCH 2/9] block/qcow2: use buffer-based io Vladimir Sementsov-Ogievskiy
2019-04-22 14:58   ` Vladimir Sementsov-Ogievskiy
2019-04-22 14:58 ` [Qemu-devel] [PATCH 3/9] block/qcow: " Vladimir Sementsov-Ogievskiy
2019-04-22 14:58   ` Vladimir Sementsov-Ogievskiy
2019-04-22 14:58 ` [Qemu-devel] [PATCH 4/9] block/qed: " Vladimir Sementsov-Ogievskiy
2019-04-22 14:58   ` Vladimir Sementsov-Ogievskiy
2019-04-30 10:46   ` Kevin Wolf
2019-04-30 10:46     ` Kevin Wolf
2019-04-22 14:58 ` [Qemu-devel] [PATCH 5/9] block/parallels: " Vladimir Sementsov-Ogievskiy
2019-04-22 14:58   ` Vladimir Sementsov-Ogievskiy
2019-04-22 14:58 ` [Qemu-devel] [PATCH 6/9] block/backup: " Vladimir Sementsov-Ogievskiy
2019-04-22 14:58   ` Vladimir Sementsov-Ogievskiy
2019-04-22 14:58 ` [Qemu-devel] [PATCH 7/9] block/commit: " Vladimir Sementsov-Ogievskiy
2019-04-22 14:58   ` Vladimir Sementsov-Ogievskiy
2019-04-22 14:58 ` [Qemu-devel] [PATCH 8/9] block/stream: " Vladimir Sementsov-Ogievskiy
2019-04-22 14:58   ` Vladimir Sementsov-Ogievskiy
2019-04-22 14:58 ` [Qemu-devel] [PATCH 9/9] qemu-img: " Vladimir Sementsov-Ogievskiy
2019-04-22 14:58   ` Vladimir Sementsov-Ogievskiy
2019-04-23 13:06 ` [Qemu-devel] [PATCH 0/9] block: " Stefan Hajnoczi
2019-04-23 13:06   ` Stefan Hajnoczi
2019-04-23 16:20   ` Vladimir Sementsov-Ogievskiy
2019-04-23 16:20     ` Vladimir Sementsov-Ogievskiy
2019-04-30  9:38 ` Stefano Garzarella
2019-04-30  9:38   ` Stefano Garzarella
2019-04-30  9:46   ` Vladimir Sementsov-Ogievskiy
2019-04-30  9:46     ` Vladimir Sementsov-Ogievskiy
2019-04-30 10:52 ` Kevin Wolf [this message]
2019-04-30 10:52   ` Kevin Wolf

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=20190430105256.GE5607@linux.fritz.box \
    --to=kwolf@redhat.com \
    --cc=den@openvz.org \
    --cc=jsnow@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vsementsov@virtuozzo.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.