From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754516Ab0KLHqB (ORCPT ); Fri, 12 Nov 2010 02:46:01 -0500 Received: from 0122700014.0.fullrate.dk ([95.166.99.235]:43990 "EHLO kernel.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751289Ab0KLHqA (ORCPT ); Fri, 12 Nov 2010 02:46:00 -0500 Message-ID: <4CDCF0B4.9070508@kernel.dk> Date: Fri, 12 Nov 2010 08:45:56 +0100 From: Jens Axboe MIME-Version: 1.0 To: Jeremy Fitzhardinge CC: "\"Xen-devel@lists.xensource.com\" li" , Linux Kernel Mailing List , Christoph Hellwig , Daniel Stodden Subject: Re: [GIT PULL] xen blkfront barrier updates References: <4CDC7A3C.8070206@goop.org> In-Reply-To: <4CDC7A3C.8070206@goop.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2010-11-12 00:20, Jeremy Fitzhardinge wrote: > Hi Jens, > > Here's the xen-blkfront barrier changes we discussed in Boston (its > identical to the last posted version). > > The only comment was Christoph pointing out EOPNOTSUPP is not used in > the block interface, but blkfront is just using it as a local > placeholder and it never gets returned up to the block layer. > > I still haven't sorted out what's going on with the backends; we > definitely need either a FLUSH operation or make empty WRITE_BARRIER > work to flush disk caches. Thanks Jeremy, I'll pull this in. -- Jens Axboe