linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dirk W. Steinberg" <dws@dirksteinberg.de>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Swapping for diskless nodes
Date: Thu, 09 Aug 2001 09:51:42 +0100	[thread overview]
Message-ID: <3B724F1E.F354795E@dirksteinberg.de> (raw)

Hi,

what is the best/recommended way to do remote swapping via the network
for diskless workstations or compute nodes in clusters in Linux 2.4? 
Last time i checked was linux 2.2, and there were some races related 
to network swapping back then. Has this been fixed for 2.4?

What about the following options: Do they work at all? What are the advantages/
disadvantages? What are the performance implications? Race conditions?

1. Swapping via NFS? There was a patch for this for 2.2? Is there such a
   patch for 2.4 as well? Should one use UDP or TCP? NFSv2? NFSv3?

2. Using some sort of network block device (nbd, new nbd, gnbd, drbd, 
   possibly others?). Which one to use? I suspect that for performance
   a kernel mode implementation is needed for both client and server.

3. iSCSI. There are several implementations, and I don't know if any of 
   these is ready for production use. Both initiator and target 
   implementation would be needed because I don't have any native iSCSI
   targets available.

4. Swapping to GFS? Is that possible? Even if GFS is based on gnbd, not FC?

5. Anything else? Maybe some implementation of network memory in the context
   of a cluster computing environment (MOSIX, etc.).

Thanks for any answers.

Cheers,
	Dirk

------------------------------------------
Ingenieurbüro Dipl.-Ing. Dirk W. Steinberg
Ringstr. 2, D-53567 Buchholz, Germany
Phone: +49-2683-9793-20, fax: -29
Mobile/GSM: +49-170-818-9793
Email: dws@dirksteinberg.de

             reply	other threads:[~2001-08-09  9:00 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-09  8:51 Dirk W. Steinberg [this message]
     [not found] <no.id>
2001-08-09  9:08 ` Swapping for diskless nodes Alan Cox
2001-08-09 10:50   ` Ingo Oeser
2001-08-09 13:12     ` Dirk W. Steinberg
2001-08-09 20:47     ` Rik van Riel
2001-08-09 14:17   ` Dirk W. Steinberg
2001-08-09 14:36     ` Andreas Haumer
2001-08-11  1:11       ` Pavel Machek
2001-08-09 19:27   ` Pavel Machek
2001-08-09 20:38   ` Rik van Riel
2001-08-09 15:14 ` Alan Cox
2001-08-11  1:17   ` Pavel Machek
2001-08-09 15:19 ` Alan Cox
2001-08-09 17:09   ` Eric W. Biederman
2001-08-09 20:58     ` Rik van Riel
2001-08-10  8:11       ` Eric W. Biederman
2001-08-09 14:26 Bulent Abali
2001-08-09 15:13 ` Alan Cox
2001-08-09 20:57   ` Rik van Riel
2001-08-09 22:46     ` Alan Cox
2001-08-11  1:16       ` Pavel Machek
2001-08-11  1:13   ` Pavel Machek
2001-08-14 12:57     ` Alan Cox
2001-08-16 21:46       ` Pavel Machek
2001-08-17  0:46         ` Rik van Riel
2001-08-17  1:35           ` Jakob Østergaard
2001-08-17 21:23             ` Pavel Machek
2001-08-17  6:42           ` Andreas Haumer
2001-08-17 21:25             ` Pavel Machek
2001-08-17 21:03           ` Andreas Haumer
2001-08-17 22:31             ` Dirk W. Steinberg
2001-08-17 22:57               ` Pavel Machek

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=3B724F1E.F354795E@dirksteinberg.de \
    --to=dws@dirksteinberg.de \
    --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 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).