From: Andrew Morton <akpm@osdl.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org
Subject: Re: page migration: Fail with error if swap not setup
Date: Tue, 14 Mar 2006 19:52:34 -0800 [thread overview]
Message-ID: <20060314195234.10cf35a7.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0603141945060.24395@schroedinger.engr.sgi.com>
Christoph Lameter <clameter@sgi.com> wrote:
>
> On Tue, 14 Mar 2006, Andrew Morton wrote:
>
> > Christoph Lameter <clameter@sgi.com> wrote:
> > >
> > > Currently the migration of anonymous pages will silently fail if no swap
> > > is setup.
> >
> > Why?
>
> The allocation of the swap page will fail in migrate_pages() and then the
> page is going on the permant failure list. Hmm... This is not a real
> total failure of page migration since file backed pages can be migrated
> without having swap and page migration will continue for those. However,
> all anonymous pages will end up on the failed list. At the end of page
> migration these will be returned to the LRU. Thus they stay where they
> were.
>
> > I mean, if something tries to allocate a swap page and that fails then the
> > error should be propagated back. That's race-free.
>
> It is propaged back in the form of a list of pages that failed to migrate.
> Its just no clear at the end what the reasons for the individual failures
> were. Its better just to check for swap availability before migration.
But the operation can still fail if we run out of swapspace partway through
- so this problem can still occur. The patch just makes it (much) less
frequent.
Surely it's possible to communicate -ENOSWAP correctly and reliably?
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-03-15 3:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 3:05 Christoph Lameter
2006-03-15 3:24 ` Andrew Morton
2006-03-15 3:49 ` Christoph Lameter
2006-03-15 3:52 ` Andrew Morton [this message]
2006-03-15 3:59 ` Christoph Lameter
2006-03-15 12:49 ` Nick Piggin
2006-03-15 16:35 ` Christoph Lameter
2006-03-15 3:53 ` Christoph Lameter
2006-03-15 14:47 ` Lee Schermerhorn
2006-03-15 17:11 ` Christoph Lameter
2006-03-15 20:47 ` Marcelo Tosatti
2006-03-15 18:08 ` Christoph Lameter
2006-03-15 21:39 ` Marcelo Tosatti
2006-03-15 19:00 ` Christoph Lameter
2006-03-15 23:06 ` Marcelo Tosatti
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=20060314195234.10cf35a7.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=clameter@sgi.com \
--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