[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <987664A83D2D224EAE907B061CE93D530191F27E0E@orsmsx505.amr.corp.intel.com>
Date: Wed, 1 Dec 2010 22:00:12 -0800
From: "Luck, Tony" <tony.luck@...el.com>
To: Andrew Morton <akpm@...ux-foundation.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...e.hu" <mingo@...e.hu>, "greg@...ah.com" <greg@...ah.com>,
"Huang, Ying" <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>
Subject: RE: [RFC] persistent store (version 2) (part 1 of 2)
> filenames refer to files! And lo, that's what we have here. A
> filesystem! The files are created by the kernel and are read and
> unlinked by userspace.
>
> So why not implement this whole thing as a proper filesystem?
...
> Wait. It *is* a filesystem.
...
> So why can't I remove these "records" with rm?
Because I tried to use /sys for this and couldn't find a
way to get notified about "unlink". Alan Cox called this
bit "daft" in v1 (and I agreed with him). Peter Anvin gave
me some pointers on how easy this would be to do as a real
filesystem ... so v3 will be out in a little while with
this insanity removed.
I'll roll in fixes to address your other comments too.
Thanks for the review.
-Tony
--
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