From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: Re: Swapping for diskless nodes
Date: Thu, 9 Aug 2001 12:50:33 +0200 [thread overview]
Message-ID: <20010809125033.E1200@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <E15Ulnx-0006zZ-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Aug 09, 2001 at 10:08:37AM +0100
On Thu, Aug 09, 2001 at 10:08:37AM +0100, Alan Cox wrote:
> > 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?=20
> > Last time i checked was linux 2.2, and there were some races related=20
> > to network swapping back then. Has this been fixed for 2.4?
>
> The best answer probably is "don't". Networks are high latency things for
> paging and paging is latency sensitive. If performance is not an issue then
> the nbd driver ought to work. You may need to check it uses the right
> GFP_ levels to avoid deadlocks and you might need to up the amount of atomic
> pool memory. Hopefully other hacks arent needed
While we are on it: I have an old machine with 64MB of RAM and a
new, fast machine with 1GB of RAM.
Sometimes I need more RAM on the old one and asked myself,
whether I could first swap over network to the other one, into
its tmpfs, before digging into real swap on a hard disk.
I have only three machines attached to this small internal
100Mbit LAN.
Both machines use Kernel 2.4.x.
Are there any races I have to consider?
Thanks & Regards
Ingo Oeser
--
In der Wunschphantasie vieler Mann-Typen [ist die Frau] unsigned und
operatorvertraeglich. --- Dietz Proepper in dasr
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next parent reply other threads:[~2001-08-09 10:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <no.id>
[not found] ` <E15Ulnx-0006zZ-00@the-village.bc.nu>
2001-08-09 10:50 ` Ingo Oeser [this message]
2001-08-09 13:12 ` Dirk W. Steinberg
2001-08-09 20:47 ` Rik van Riel
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
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=20010809125033.E1200@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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