From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-mm@kvack.org
Subject: Re: page migration: Fail with error if swap not setup
Date: Wed, 15 Mar 2006 23:49:30 +1100 [thread overview]
Message-ID: <44180D5A.7000202@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0603141955370.24487@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
> On Tue, 14 Mar 2006, Andrew Morton wrote:
>
>
>>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?
>
>
> There are a number of possible failure conditions. The strategy of the
> migration function is to migrate as much as possible and return the rest
> without giving any reason. migrate_pages() returns the number of leftover
> pages not the reasons they failed.
>
Could you return the reason the first failing page failed. At least then
the caller can have some idea about what is needed to make further progress.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
--
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 12:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 3:05 page migration: Fail with error if swap not setup Christoph Lameter
2006-03-15 3:24 ` Andrew Morton
2006-03-15 3:49 ` Christoph Lameter
2006-03-15 3:52 ` Andrew Morton
2006-03-15 3:59 ` Christoph Lameter
2006-03-15 12:49 ` Nick Piggin [this message]
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=44180D5A.7000202@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.