[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTimA4x8oWyq71nOxB=Otp3Y0i3Kcu27DG0ajaXUG@mail.gmail.com>
Date: Fri, 17 Dec 2010 13:38:12 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Tony Luck <tony.luck@...el.com>
Cc: linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
tglx@...utronix.de, mingo@...e.hu, greg@...ah.com,
akpm@...ux-foundation.org, ying.huang@...el.com,
Borislav Petkov <bp@...en8.de>,
David Miller <davem@...emloft.net>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Jim Keniston <jkenisto@...ux.vnet.ibm.com>,
Kyungmin Park <kmpark@...radead.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [concept & "good taste" review] persistent store
On Fri, Dec 17, 2010 at 10:09 AM, Tony Luck <tony.luck@...el.com> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists