From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [sqlite] light weight write barriers Date: Thu, 11 Oct 2012 13:41:57 -0400 Message-ID: <20121011174157.GA32038@infradead.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: General Discussion of SQLite Database , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, drh@hwaci.com To: ????????? Yang Su Li Return-path: Received: from 173-166-109-252-newengland.hfc.comcastbusiness.net ([173.166.109.252]:50476 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964797Ab2JKRmE (ORCPT ); Thu, 11 Oct 2012 13:42:04 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Oct 11, 2012 at 11:32:27AM -0500, ????????? Yang Su Li wrote: > I am not quite whether I should ask this question here, but in terms > of light weight barrier/fsync, could anyone tell me why the device > driver / OS provide the barrier interface other than some other > abstractions anyway? I am sorry if this sounds like a stupid questions > or it has been discussed before.... It does not. Except for the legacy mount option naming there is no such thing as a barrier in Linux these days.