From: David Collier-Brown <davecb@sun.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Willy Tarreau" <w@1wt.eu>, "Jörn Engel" <joern@logfs.org>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Andrew Morton" <akpm@linux-foundation.org>,
"David Woodhouse" <dwmw2@infradead.org>,
"Arnd Bergmann" <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Offtopic to: LogFS merge
Date: Sat, 03 May 2008 13:59:46 -0400 [thread overview]
Message-ID: <481CA812.2030404@sun.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0805031014300.5994@woody.linux-foundation.org>
Linus Torvalds wrote:
> The real issue for me wrt a filesystem is the on-disk layout.
>
> If we know that on-disk structures need change, we shouldn't merge it. It
> doesn't matter if that can be worked around with some backwards-
> compatibiltiy flag: we should simply not encourage that kind of behaviour.
I agree in particular, but not in principle (;-))
Changing the filesystem format was something that happened at
least twice on Multics, on production machines. I happened to be
on during one of the changes and didn't even know it was happening
until there was a broadcast message warning of poor performance.
I always thought that was cool, and got permission recently to
post a colleague's paper on it at http://www.multicians.org/stachour.html
It would be cool if data could change at run-time on Linux, just
like security-sensitive code.
--dave
--
David Collier-Brown | Always do right. This will gratify
Sun Microsystems, Toronto | some people and astonish the rest
davecb@sun.com | -- Mark Twain
(905) 943-1983, cell: (647) 833-9377, (800) 555-9786 x56583
bridge: (877) 385-4099 code: 506 9191#
next prev parent reply other threads:[~2008-05-03 18:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 13:32 LogFS merge Jörn Engel
2008-05-02 14:49 ` Pekka Enberg
2008-05-02 15:31 ` Christoph Hellwig
2008-05-02 20:33 ` Jörn Engel
2008-05-02 16:52 ` Arnd Bergmann
2008-05-02 21:47 ` Jörn Engel
2008-05-02 17:17 ` Linus Torvalds
2008-05-02 20:21 ` Jörn Engel
2008-05-02 20:33 ` Linus Torvalds
2008-05-02 21:31 ` Jörn Engel
2008-05-02 21:39 ` Linus Torvalds
2008-05-02 21:58 ` Jörn Engel
2008-05-03 7:03 ` Willy Tarreau
2008-05-03 9:11 ` Adrian Bunk
2008-05-03 9:18 ` Willy Tarreau
2008-05-03 9:37 ` Adrian Bunk
2008-05-03 9:44 ` Pekka Enberg
2008-05-03 11:06 ` Adrian Bunk
2008-05-03 17:16 ` Linus Torvalds
2008-05-03 17:59 ` David Collier-Brown [this message]
2008-05-02 17:29 ` Andi Kleen
2008-05-02 21:34 ` Jörn Engel
2008-05-05 20:31 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=481CA812.2030404@sun.com \
--to=davecb@sun.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dwmw2@infradead.org \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox