Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752494Ab2KQFC6 (ORCPT ); Sat, 17 Nov 2012 00:02:58 -0500 Received: from moutng.kundenserver.de ([212.227.126.186]:62520 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750728Ab2KQFC4 (ORCPT ); Sat, 17 Nov 2012 00:02:56 -0500 Message-ID: <50A71A74.7040706@vlnb.net> Date: Sat, 17 Nov 2012 00:02:44 -0500 From: Vladislav Bolkhovitin User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.28) Gecko/20120313 Mnenhy/0.8.5 Thunderbird/3.1.20 MIME-Version: 1.0 To: =?UTF-8?B?5p2o6IuP56uLIFlhbmcgU3UgTGk=?= CC: General Discussion of SQLite Database , "Theodore Ts'o" , Richard Hipp , linux-kernel , linux-fsdevel@vger.kernel.org Subject: Re: [sqlite] light weight write barriers References: <5086F5A7.9090406@vlnb.net> <20121025051445.GA9860@thunk.org> <508B3EED.2080003@vlnb.net> <20121027044456.GA2764@thunk.org> <5090532D.4050902@vlnb.net> <20121031095404.0ac18a4b@pyramind.ukuu.org.uk> <5092D90F.7020105@vlnb.net> <20121101212418.140e3a82@pyramind.ukuu.org.uk> <50931601.4060102@symas.com> <20121102123359.2479a7dc@pyramind.ukuu.org.uk> <50A1C15E.2080605@vlnb.net> <20121113174000.6457a68b@pyramind.ukuu.org.uk> <50A442AF.9020407@vlnb.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Provags-ID: V02:K0:VjjA/PgoHtzuYldPFVfFuBjAvGEE5HAB03y7kLj557P 7F0QNEqi8gct93DFADNMWpxbHiT9Npaptc9AB1WemM9eN1RIxM ue5tPlcBJIlUD09tG5C6B0P4bP+JokeGW8EeecE7nmfc/crENP Xx64lpBMj6ZGi2IpniEUfFSY57JtY5BweHkpTTOz5CQsgP/6sF UECfofvRQT5GCUAKLRCyRwDg7tcElcmLUtkuVSIveHe0YTC7O3 onOr7qScavwSy9RhcVsud/Hh3MKMpyTi5Bicsg4QYsuUO0Hx27 KiN+2Fg2eWk21L4YjpQtxPk14yzug/VXrlSiTAvFg7V781lFkt UP/xDi8iFjKjNSsUEefM= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 787 Lines: 21 杨苏立 Yang Su Li, on 11/15/2012 11:14 AM wrote: > 1. fsync actually does two things at the same time: ordering writes (in a > barrier-like manner), and forcing cached writes to disk. This makes it very > difficult to implement fsync efficiently. Exactly! > However, logically they are two distinctive functionalities Exactly! Those two points are exactly why concept of barriers must be forgotten for sake of productivity and be replaced by a finer grained abstractions as well as why they where removed from the Linux kernel Vlad -- 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/