Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754514AbZC3PXQ (ORCPT ); Mon, 30 Mar 2009 11:23:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752888AbZC3PWp (ORCPT ); Mon, 30 Mar 2009 11:22:45 -0400 Received: from mail-bw0-f169.google.com ([209.85.218.169]:34580 "EHLO mail-bw0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751293AbZC3PWn convert rfc822-to-8bit (ORCPT ); Mon, 30 Mar 2009 11:22:43 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:message-id; b=wMFfJrBDl1mjlrRlwQIX2x75Cmm6BdU+Xv/C4lGeorihg005EPW9LxIbke6vcIlOMA iEJcqMQrAdCzBef81isbTRMC7Iohtb+LWRnoFd/vc5Jqy+w/cjk5iEBrUlQxo3g+6Hk5 LN+gUQ3/nYYW/EOZ3gF0uubpWHiXud2C9HNTA= From: Bartlomiej Zolnierkiewicz To: Fernando Luis =?iso-8859-1?q?V=E1zquez_Cao?= Subject: Re: [PATCH 5/7] vfs: Add wbcflush sysfs knob to disable storage device writeback cache flushes Date: Mon, 30 Mar 2009 17:14:08 +0200 User-Agent: KMail/1.11.1 (Linux/2.6.29-next-20090327-dirty; KDE/4.2.1; i686; ; ) Cc: Jeff Garzik , Christoph Hellwig , Linus Torvalds , Theodore Tso , Ingo Molnar , Alan Cox , Arjan van de Ven , Andrew Morton , Peter Zijlstra , Nick Piggin , David Rees , Jesper Krogh , Linux Kernel Mailing List , chris.mason@oracle.com, david@fromorbit.com, tj@kernel.org References: <49D0B535.2010106@oss.ntt.co.jp> <49D0B978.5030107@oss.ntt.co.jp> In-Reply-To: <49D0B978.5030107@oss.ntt.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT Content-Disposition: inline Message-Id: <200903301714.13174.bzolnier@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 754 Lines: 17 On Monday 30 March 2009, Fernando Luis V?zquez Cao wrote: > Add a sysfs knob to disable storage device writeback cache flushes. The horde of casual desktop users (with me included) would probably prefer having two settings -- one for filesystem barriers and one for fsync(). IOW I prefer higher performance at the cost of risking losing few last seconds/minutes of work in case of crash / powerfailure but I would still like to have the filesystem in the consistent state after such accident. Thanks, Bart -- 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/