From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756598Ab0LQViq (ORCPT ); Fri, 17 Dec 2010 16:38:46 -0500 Received: from smtp1.linux-foundation.org ([140.211.169.13]:33139 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755862Ab0LQVik (ORCPT ); Fri, 17 Dec 2010 16:38:40 -0500 MIME-Version: 1.0 In-Reply-To: References: <4d0662e511688484b3@agluck-desktop.sc.intel.com> From: Linus Torvalds Date: Fri, 17 Dec 2010 13:38:12 -0800 Message-ID: Subject: Re: [concept & "good taste" review] persistent store To: Tony Luck Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, tglx@linutronix.de, mingo@elte.hu, greg@kroah.com, akpm@linux-foundation.org, ying.huang@intel.com, Borislav Petkov , David Miller , Alan Cox , Jim Keniston , Kyungmin Park , Geert Uytterhoeven , "H. Peter Anvin" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 17, 2010 at 10:09 AM, Tony Luck wrote: > > So does fixing this stupidity provide a useful point for this? Yes. However, I still question the "filesystem" part. Technically, what I think any persistent storage should aim for is to be a "journal" - not a filesystem. It's most useful as a temporary area for data _before_ that data actually hits the disk, and once it has hit the disk (or has been picked up by a network syslog server, of course), the usefulness of the persistent storage immediately vanishes. So I don't really mind having a filesystem interface to that (the whole "everything is a file" model), but I think it can end up confusing people about what this thing is useful for. I fear that people will try to write to it from user space as some kind of mini-filesystem, and that seems pointless. Linus