From: ebiederm@xmission.com (Eric W. Biederman)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Dirk W. Steinberg" <dws@dirksteinberg.de>,
Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Swapping for diskless nodes
Date: 09 Aug 2001 11:09:37 -0600 [thread overview]
Message-ID: <m1snf1tb1q.fsf@frodo.biederman.org> (raw)
In-Reply-To: <E15UrbB-0007T9-00@the-village.bc.nu>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> > the memory of a fast server could have much less latency that writing
> > that page out to a local old, slow IDE disk. Clusters could even have
> > special high-bandwidth, low latency networks that could be used for
> > remote paging.
> >
> > In a perfect world, all nodes in a cluster would be able to dynamically
> > share a pool of "cluster swap" space, so any locally available swap that
> > is not used could be utilized by other nodes in the cluster.
>
> That I think is a 2.5 problem. One thing that has been talked about several
> times now is removing all the swap special case crap from the mm and making
> swap a file system. That removes special cases and means anyone can write
> or use custom, or multiple swap filesystems, in theory including things like
> swap over a shared GFS pool
>
> But its not for 2.4, no way
I don't know about that. We already can swap over just about everything
because we can swap over the loopback device. So moving making the swapping
code do the right thing is not that big of an allowance, nor that
much of extra code so if 2.5 actually starts up I can see us doing that.
Eric
--
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 prev parent reply other threads:[~2001-08-09 17:09 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
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 [this message]
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=m1snf1tb1q.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dws@dirksteinberg.de \
--cc=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