Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964857Ab2JKRmI (ORCPT ); Thu, 11 Oct 2012 13:42:08 -0400 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 Date: Thu, 11 Oct 2012 13:41:57 -0400 From: Christoph Hellwig To: ????????? Yang Su Li Cc: General Discussion of SQLite Database , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, drh@hwaci.com Subject: Re: [sqlite] light weight write barriers Message-ID: <20121011174157.GA32038@infradead.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 747 Lines: 15 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. -- 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/