From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34982) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1agYbx-0000tu-QJ for qemu-devel@nongnu.org; Thu, 17 Mar 2016 10:09:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1agYbu-0000ou-0B for qemu-devel@nongnu.org; Thu, 17 Mar 2016 10:09:13 -0400 Date: Thu, 17 Mar 2016 15:08:57 +0100 From: Kevin Wolf Message-ID: <20160317140857.GB4833@noname.redhat.com> References: <1457441273-29821-1-git-send-email-kwolf@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1457441273-29821-1-git-send-email-kwolf@redhat.com> Subject: Re: [Qemu-devel] [PATCH 0/8] block: Introduce common read/write function List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-block@nongnu.org Cc: qemu-devel@nongnu.org, stefanha@redhat.com, mreitz@redhat.com Am 08.03.2016 um 13:47 hat Kevin Wolf geschrieben: > BlockBackends support a few different interfaces for reads and writes. Until > now they used to forward the requests directly to the BDS layer, which > implemented wrappers around one central common read/write function that > contained the actual implementation of features provided by the block layer. > > This only works as long as none of the features are actually on the > BlockBackend level. As it happens, we have features (writethrough cache, I/O > throttling) that are currently implemented in the BDS, but must move to the BB. > > As a preparation, this series introduces the mapping of the existing APIs to a > single coroutine based preadv/pwritev function (as we already have on the BDS > level) to the BB layer. The BDS version of the emulation can't go away just yet > because there are internal users of them, but the goal is to remove them in the > long term. > > Depends on Max's "blockdev: Further BlockBackend work". Applied to the block branch. Kevin