qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v2 0/5] block: do request processing in a corout


From: Kevin Wolf
Subject: Re: [Qemu-devel] [PATCH v2 0/5] block: do request processing in a coroutine
Date: Thu, 13 Oct 2011 15:05:10 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20110927 Thunderbird/7.0

Am 13.10.2011 14:08, schrieb Stefan Hajnoczi:
> Note: this version applies against Kevin's block tree
> 
> Block layer features like dirty block tracing, I/O throttling, and live block
> copy are forced to duplicate code due to the three different interfaces:
> synchronous, asynchronous, and coroutines.
> 
> Since there are bdrv_read(), bdrv_aio_readv(), and bdrv_co_readv() interfaces
> for read (and similar for write), per-request processing needs to be 
> duplicated
> for each of these execution contexts.  For example, dirty block tracking code
> is duplicated across these three interfaces.
> 
> This patch series unifies request processing so that there is only one code
> path.  I see this as a prerequisite to the live block copy (image streaming)
> code I am working on, so I'm pushing it now.
> 
> The short-term win from this series is that it becomes easy to add live block
> copy and other features.  We now have a single code path where the 
> perf-request
> processing is done.
> 
> The longer-term win will be dropping the BlockDriver .bdrv_read(),
> .bdrv_write(), .bdrv_aio_readv(), and .bdrv_aio_writev() interfaces.  By doing
> that we can bring all BlockDrivers onto a common interface, namely
> .bdrv_co_readv() and .bdrv_co_writev().  It will also allow us to drop most of
> the sync and aio emulation code.
> 
> A consequence of this patch series is that every I/O request goes through at
> least one coroutine.  There is no longer a direct .bdrv_read(), .bdrv_write(),
> .bdrv_aio_readv(), or .bdrv_aio_writev() call - we're trying to phase out 
> those
> interfaces.  I have not noticed performance degradation in correctness tests
> but we need to confirm that there has not been a performance regression.
> 
> v2:
>  * Fixed bdrv_read()/bdrv_write() infinite loop [Kevin]
> 
> Stefan Hajnoczi (5):
>   block: directly invoke .bdrv_* from emulation functions
>   block: switch bdrv_read()/bdrv_write() to coroutines
>   block: switch bdrv_aio_readv() to coroutines
>   block: mark blocks dirty on coroutine write completion
>   block: switch bdrv_aio_writev() to coroutines
> 
>  block.c |  245 ++++++++++++++++++++++++++++----------------------------------
>  1 files changed, 111 insertions(+), 134 deletions(-)

Thanks, applied to the block branch.

I think there's some dead code now, but we can leave the clean-up for later.

Kevin



reply via email to

[Prev in Thread] Current Thread [Next in Thread]