From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Stroetmann Subject: Re: Atomic non-durable file write API Date: Fri, 24 Dec 2010 12:29:39 +0100 Message-ID: <4D148423.6090500@ontolinux.com> 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; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-fsdevel , Ted Ts'o , Neil Brown To: Olaf van der Spek Return-path: Received: from moutng.kundenserver.de ([212.227.126.171]:49603 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750836Ab0LXL3i (ORCPT ); Fri, 24 Dec 2010 06:29:38 -0500 In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On 24.12.2010 12:17, Olaf van der Spek wrote: > 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. You 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. From the flow of the discussion I guess you should give R4 a try. > Olaf > -- Christian Stroetmann