From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: Proposal to improve filesystem/block snapshot interaction Date: Tue, 30 Oct 2007 13:38:55 +0100 Message-ID: <200710301338.56592.arnd@arndb.de> References: <20070927063113.GD2989@sgi.com> <200710301115.30376.arnd@arndb.de> <7fe698080710300349x5df5d9b9kb3bd69a3077940bc@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: "Greg Banks" , "Linux Filesystem Mailing List" , "David Chinner" , "Donald Douwsma" , "Christoph Hellwig" , "Roger Strassburg" , "Mark Goodwin" , "Brett Jon Grandbois" To: "Dongjun Shin" Return-path: Received: from moutng.kundenserver.de ([212.227.126.183]:50730 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751989AbXJ3MjU (ORCPT ); Tue, 30 Oct 2007 08:39:20 -0400 In-Reply-To: <7fe698080710300349x5df5d9b9kb3bd69a3077940bc@mail.gmail.com> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Tuesday 30 October 2007, Dongjun Shin wrote: > Anyway, BIO_HINT_RELEASE could destroy the content of the blocks > after being passed to the device. I think that other bio should not be > reordered accross that hint (just like barrier). Not sure. Why shouldn't you be able to reorder the hints provided that they don't overlap with read/write bios for the same block? Arnd <><