linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ric Wheeler <ric@emc.com>
To: "David L. Nicol" <david@kasey.umkc.edu>
Cc: Zack Brown <zbrown@tumblerings.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-cluster@nl.linux.org
Subject: Re: Will Mosix go into the standard kernel?
Date: Wed, 28 Feb 2001 12:59:58 -0500	[thread overview]
Message-ID: <3A9D3C9E.6090807@emc.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1010227091255.780M-100000@renegade> <3A9C1A3A.8BC1BCF2@kasey.umkc.edu>

There are two parts of MOSIX that deal with file systems.
In MOSIX, every migrated process leaves a proxy at its creation (home)
node that services all system call requests, including IO calls.

What newer versions of MOSIX did is to add the "DFSA" (direct file
system access) layer that allows MOSIX to support executing file
system calls locally for migrated process when they are against a
cache coherent, cluster file system (think GFS).  When this was put
in MOSIX, they also did a write through, non-caching file system to
test their DFSA code called MFS.

Both the MOSIX team and the global file system group have been involved
in getting their stuff to play nicely together.

ric





  parent reply	other threads:[~2001-02-28 18:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27 17:17 Will Mosix go into the standard kernel? Zack Brown
2001-02-27 21:20 ` David L. Nicol
2001-02-27 21:32   ` Rik van Riel
2001-02-28 23:06     ` Daniel Ridge
2001-02-28 23:58       ` Albert D. Cahalan
2001-03-01  0:53         ` Dan Hollis
2001-03-01  1:35         ` Daniel Ridge
2001-03-01  2:37       ` zbrown
2001-03-02  0:52       ` Pavel Machek
2001-02-27 21:37   ` Alexander Viro
2001-02-27 21:56   ` Zack Brown
2001-02-27 22:29     ` zbrown
2001-02-27 22:33     ` J . A . Magallon
2001-02-28 17:59   ` Ric Wheeler [this message]
2001-02-27 17:31 Christopher Chimelis
2001-02-27 17:40 ` Zack Brown
     [not found] <fa.o4k0c0v.smgv2v@ifi.uio.no>
     [not found] ` <fa.m9jgfcv.17n8s2n@ifi.uio.no>
2001-03-01 15:02   ` Tor Arntsen
2001-03-01 19:13     ` Tim Wright
2001-03-02 10:22 Tor Arntsen

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=3A9D3C9E.6090807@emc.com \
    --to=ric@emc.com \
    --cc=david@kasey.umkc.edu \
    --cc=linux-cluster@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zbrown@tumblerings.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).