From: Olaf van der Spek Subject: Re: Atomic non-durable file write API Date: Fri, 24 Dec 2010 12:17:46 +0100 Message-ID: References: <4D0A7278.3080506@gmail.com> <1292710543.17128.14.camel@nayuki> <20101224085126.2a7ff187@notabene.brown> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org To: Neil Brown Return-path: Received: from mail-fx0-f46.google.com ([209.85.161.46]:50155 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751713Ab0LXLRs convert rfc822-to-8bit (ORCPT ); Fri, 24 Dec 2010 06:17:48 -0500 In-Reply-To: <20101224085126.2a7ff187@notabene.brown> Sender: linux-ext4-owner@vger.kernel.org List-ID: On Thu, Dec 23, 2010 at 10:51 PM, Neil Brown wrote: > You are asking for something that doesn't exist, which is why no-one = can tell > you want the answer is. It seems like a very common and basic operation. If it doesn't exist IMO it should be created. > The only mechanism for synchronising different filesystem operations = is > fsync. =C2=A0You should use that. > > If it is too slow, use data journalling, and place your journal on a > small low-latency device (NVRAM??) This isn't about some DB-like app, it's about normal file writes, like archive extractions, compiling, editors, etc. Olaf -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html