From: Dave Hansen <haveblue@us.ibm.com>
To: Paul Jackson <pj@engr.sgi.com>
Cc: mel@csn.ul.ie, linux-mm <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 0/2 Buddy allocator with placement policy (Version 9) + prezeroing (Version 4)
Date: Thu, 10 Mar 2005 12:17:15 -0800 [thread overview]
Message-ID: <1110485835.24355.1.camel@localhost> (raw)
In-Reply-To: <20050310121124.488cb7c5.pj@engr.sgi.com>
On Thu, 2005-03-10 at 12:11 -0800, Paul Jackson wrote:
> Dave wrote:
> > Perhaps default policies inherited from a cpuset, but overridden by
> > other APIs would be a good compromise.
>
> Perhaps. The madvise() and numa calls (mbind, set_mempolicy) only
> affect the current task, as is usually appropriate for calls that allow
> specification of specific address ranges (strangers shouldn't be messing
> in my address space). Some external means to set default policy for
> whole tasks seems to be needed, as well, which could well be via the
> cpuset.
Shouldn't a particular task know what the policy should be when it is
launched? If the policy is only per-task and known at task exec time,
I'd imagine that a simple exec wrapper setting a flag would be much more
effective than even defining the policy in a cpuset.
-- Dave
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <haveblue@us.ibm.com>
To: Paul Jackson <pj@engr.sgi.com>
Cc: mel@csn.ul.ie, linux-mm <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 0/2 Buddy allocator with placement policy (Version 9) + prezeroing (Version 4)
Date: Thu, 10 Mar 2005 12:17:15 -0800 [thread overview]
Message-ID: <1110485835.24355.1.camel@localhost> (raw)
In-Reply-To: <20050310121124.488cb7c5.pj@engr.sgi.com>
On Thu, 2005-03-10 at 12:11 -0800, Paul Jackson wrote:
> Dave wrote:
> > Perhaps default policies inherited from a cpuset, but overridden by
> > other APIs would be a good compromise.
>
> Perhaps. The madvise() and numa calls (mbind, set_mempolicy) only
> affect the current task, as is usually appropriate for calls that allow
> specification of specific address ranges (strangers shouldn't be messing
> in my address space). Some external means to set default policy for
> whole tasks seems to be needed, as well, which could well be via the
> cpuset.
Shouldn't a particular task know what the policy should be when it is
launched? If the policy is only per-task and known at task exec time,
I'd imagine that a simple exec wrapper setting a flag would be much more
effective than even defining the policy in a cpuset.
-- Dave
--
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>
next prev parent reply other threads:[~2005-03-10 20:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 19:39 [PATCH] 0/2 Buddy allocator with placement policy (Version 9) + prezeroing (Version 4) Mel Gorman
2005-03-07 19:39 ` Mel Gorman
2005-03-07 23:59 ` Dave Hansen
2005-03-07 23:59 ` Dave Hansen
2005-03-10 14:31 ` Mel Gorman
2005-03-10 14:31 ` Mel Gorman
2005-03-10 17:22 ` Paul Jackson
2005-03-10 17:22 ` Paul Jackson
2005-03-10 18:16 ` Dave Hansen
2005-03-10 18:16 ` Dave Hansen
2005-03-10 20:11 ` Paul Jackson
2005-03-10 20:11 ` Paul Jackson
2005-03-10 20:17 ` Dave Hansen [this message]
2005-03-10 20:17 ` Dave Hansen
2005-03-10 20:54 ` Paul Jackson
2005-03-10 20:54 ` Paul Jackson
2005-03-14 14:10 ` Mel Gorman
2005-03-14 14:10 ` Mel Gorman
2005-03-14 19:10 ` Paul Jackson
2005-03-14 19:10 ` Paul Jackson
2005-03-10 17:37 ` Dave Hansen
2005-03-10 17:37 ` Dave Hansen
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=1110485835.24355.1.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=pj@engr.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.