From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jamie Lokier Subject: Re: [RFC PATCH] Filesystem Journal Notifications Date: Mon, 15 Sep 2008 14:23:57 +0100 Message-ID: <20080915132357.GA10973@shareable.org> References: <20080912220649.GB26999@apaithan-desktop.sanmateo.corp.akamai.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org, Andreas Dilger To: Abhijit Paithankar Return-path: Received: from mail2.shareable.org ([80.68.89.115]:40928 "EHLO mail2.shareable.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753555AbYIONX7 (ORCPT ); Mon, 15 Sep 2008 09:23:59 -0400 Content-Disposition: inline In-Reply-To: <20080912220649.GB26999@apaithan-desktop.sanmateo.corp.akamai.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Abhijit Paithankar wrote: > One way to do it is to fsync every few operations. However, fsync is > blocking and affects performance. > > The other (more efficient) way is to have the filesystem notify the > application when a transaction/change is written to disk. Is this more efficient than aio_fsync, and if so, why? For file writes, aio_fsync seems like a cleaner interface, and if that's not fast enough, it could be made faster - perhaps using code form this patch. (An aio_fsync_ranges would be even better). -- Jamie