linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Rik van Riel <riel@conectiva.com.br>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"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: 10 Aug 2001 02:11:46 -0600	[thread overview]
Message-ID: <m1k80ctjul.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.33L.0108091758070.1439-100000@duckman.distro.conectiva>

Rik van Riel <riel@conectiva.com.br> writes:

> On 9 Aug 2001, Eric W. Biederman wrote:
> 
> > I don't know about that.  We already can swap over just about
> > everything because we can swap over the loopback device.
> 
> Last I looked the loopback device could deadlock your
> system without you needing to swap over it ;)

It wouldn't suprise me.  But the fact remains that in 2.4 we allow it.
And if we allw it there is little excuse for doing it wrong.

Actually except for network cases it looks easier to prevent deadlocks
on the swapping path than with the loop back devices.  We can call
aops->prepare_write_out when we place the page in the swap cache
to make certain we aren't over a hole in a file, and there is room in the
filesystem to store the data.

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/

  reply	other threads:[~2001-08-10  8:11 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
2001-08-09 20:58     ` Rik van Riel
2001-08-10  8:11       ` Eric W. Biederman [this message]
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=m1k80ctjul.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 \
    --cc=riel@conectiva.com.br \
    /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