From: Hans Reiser <reiser@namesys.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] mount flag "direct" (fwd)
Date: Wed, 04 Sep 2002 17:03:16 +0400 [thread overview]
Message-ID: <3D760494.7040805@namesys.com> (raw)
In-Reply-To: 3D75F77B.9B0610F5@aitel.hist.no
I think everyone agrees that you should start with doing it for a
particular FS, and then after you have done it for one, you will know
enough about what needs to be done that you can make your case that it
should be done in VFS. Frankly, I think that you should either share
caches between nodes (NUMA), or (somehow, and there are so many ways...)
divide the workload between the machines such that they don't access the
same data except in response to failure.
Hans
next prev parent reply other threads:[~2002-09-04 12:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 15:39 [RFC] mount flag "direct" (fwd) Peter T. Breuer
2002-09-03 15:44 ` Rik van Riel
2002-09-03 15:50 ` Peter T. Breuer
2002-09-03 15:56 ` Chris Wedgwood
2002-09-03 15:59 ` Peter T. Breuer
2002-09-03 16:09 ` Richard B. Johnson
2002-09-03 16:29 ` Peter T. Breuer
2002-09-03 16:33 ` Rik van Riel
2002-09-03 17:32 ` Richard B. Johnson
2002-09-03 18:53 ` Lars Marowsky-Bree
2002-09-03 21:07 ` Peter T. Breuer
2002-09-03 21:15 ` Andreas Dilger
2002-09-03 21:15 ` Rik van Riel
2002-09-03 21:54 ` Anton Altaparmakov
2002-09-03 22:46 ` Andreas Dilger
2002-09-03 23:19 ` Daniel Phillips
2002-09-04 0:18 ` Anton Altaparmakov
2002-09-04 5:23 ` David Lang
2002-09-04 7:16 ` Helge Hafting
2002-09-04 8:39 ` Andreas Dilger
2002-09-04 12:07 ` Helge Hafting
2002-09-04 13:03 ` Hans Reiser [this message]
2002-09-04 8:41 ` Peter T. Breuer
2002-09-04 7:50 ` Joachim Breuer
[not found] ` <3D75F8B0.8C7E974E@aitel.hist.no>
2002-09-04 21:26 ` Joachim Breuer
2002-09-04 9:26 ` Lars Marowsky-Bree
2002-09-03 16:58 ` Anton Altaparmakov
2002-09-03 17:26 ` Peter T. Breuer
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=3D760494.7040805@namesys.com \
--to=reiser@namesys.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.