Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758411AbZCZCsj (ORCPT ); Wed, 25 Mar 2009 22:48:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752238AbZCZCsa (ORCPT ); Wed, 25 Mar 2009 22:48:30 -0400 Received: from cavan.codon.org.uk ([93.93.128.6]:45668 "EHLO vavatch.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751039AbZCZCsa (ORCPT ); Wed, 25 Mar 2009 22:48:30 -0400 Date: Thu, 26 Mar 2009 02:47:53 +0000 From: Matthew Garrett To: Kyle Moffett Cc: Theodore Tso , Christoph Hellwig , Linus Torvalds , Jan Kara , Andrew Morton , Ingo Molnar , Alan Cox , Arjan van de Ven , Peter Zijlstra , Nick Piggin , Jens Axboe , David Rees , Jesper Krogh , Linux Kernel Mailing List Subject: Re: Linux 2.6.29 Message-ID: <20090326024753.GA27299@srcf.ucam.org> References: <20090324103111.GA26691@elte.hu> <20090324041249.1133efb6.akpm@linux-foundation.org> <20090325123744.GK23439@duck.suse.cz> <20090325150041.GM32307@mit.edu> <20090325185824.GO32307@mit.edu> <20090325194851.GA1617@infradead.org> <20090325215016.GP32307@mit.edu> <20090326021034.GA26559@srcf.ucam.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.12-2006-07-14 X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: mjg59@codon.org.uk X-SA-Exim-Scanned: No (on vavatch.codon.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 988 Lines: 20 On Wed, Mar 25, 2009 at 10:44:44PM -0400, Kyle Moffett wrote: > Perhaps we ought to add a couple extra open flags, O_BARRIER_BEFORE and > O_BARRIER_AFTER, and rename3(), etc functions that take flags arguments? > Or maybe a new set of syscalls like barrier(file1, file2) and > fbarrier(fd1, fd2), which cause all pending changes (perhaps limit to this > process?) to the file at fd1 to occur before any successive changes (again > limited to this process?) to the file at fd2. That's an option, but what would benefit? If rename is expected to preserve ordering (which I think it has to, in order to avoid breaking existing code) then are there any other interesting use cases? -- Matthew Garrett | mjg59@srcf.ucam.org -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/