All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Hicks <mort@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Martin Hicks <mort@sgi.com>,
	linux-mm@kvack.org, raybry@sgi.com, ak@suse.de
Subject: Re: [PATCH/RFC 4/4] VM: automatic reclaim through mempolicy
Date: Thu, 28 Apr 2005 08:56:04 -0400	[thread overview]
Message-ID: <20050428125604.GH19244@localhost> (raw)
In-Reply-To: <20050427163546.7654efc1.akpm@osdl.org>

On Wed, Apr 27, 2005 at 04:35:46PM -0700, Andrew Morton wrote:
> Martin Hicks <mort@sgi.com> wrote:
> 
> > The change required adding a "flags" argument to sys_set_mempolicy()
> > to give hints about what kind of memory you're willing to sacrifice.
> 
> This is a back-compatible change, so current userspace will continue to
> work OK, yes?

I suspect not.  sys_set_mempolicy() takes an extra arg now, so I'd guess
that it'll pull in junk for the "flags" argument during a syscall and
most likely return -EINVAL due to invalid flags (or you'll get yourself
a localreclaim policy).

Sorry for not warning about that.
mh

-- 
Martin Hicks   ||   Silicon Graphics Inc.   ||   mort@sgi.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:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2005-04-28 12:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050427145734.GL8018@localhost>
2005-04-27 15:09 ` [PATCH/RFC 1/4] VM: merge_lru_pages Martin Hicks
2005-04-27 15:09 ` [PATCH/RFC 2/4] VM: page cache reclaim core Martin Hicks
2005-04-27 23:32   ` Andrew Morton
2005-04-27 15:09 ` [PATCH/RFC 3/4] VM: toss_page_cache_node syscall Martin Hicks
2005-04-27 23:33   ` Andrew Morton
2005-04-27 15:10 ` [PATCH/RFC 4/4] VM: automatic reclaim through mempolicy Martin Hicks
2005-04-27 23:35   ` Andrew Morton
2005-04-28 12:56     ` Martin Hicks [this message]
2005-04-27 23:50   ` Andrew Morton
2005-04-28 17:41     ` Martin Hicks

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=20050428125604.GH19244@localhost \
    --to=mort@sgi.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-mm@kvack.org \
    --cc=raybry@sgi.com \
    /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.