linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Nish Aravamudan" <nish.aravamudan@gmail.com>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: Paul Mundt <lethal@linux-sh.org>, Paul Jackson <pj@sgi.com>,
	Adam Litke <agl@us.ibm.com>,
	linux-mm@kvack.org, mel@skynet.ie, apw@shadowen.org,
	wli@holomorphy.com, clameter@sgi.com, kenchen@google.com
Subject: Re: [PATCH 5/5] [hugetlb] Try to grow pool for MAP_SHARED mappings
Date: Fri, 20 Jul 2007 14:12:16 -0700	[thread overview]
Message-ID: <29495f1d0707201412y29329807v33cdf1854ade9928@mail.gmail.com> (raw)
In-Reply-To: <1184964838.9651.70.camel@localhost>

On 7/20/07, Lee Schermerhorn <Lee.Schermerhorn@hp.com> wrote:
> On Fri, 2007-07-20 at 13:35 -0700, Nish Aravamudan wrote:
> > On 7/18/07, Paul Mundt <lethal@linux-sh.org> wrote:
> <snip>
> > > It would be quite nice to have some way to have nodes opt-in to the sort
> > > of behaviour they're willing to tolerate. Some nodes are never going to
> > > tolerate spreading of any sort, hugepages, and so forth. Perhaps it makes
> > > more sense to have some flags in the pgdat where we can more strongly
> > > type the sort of behaviour the node is willing to put up with (or capable
> > > of supporting), at least in this case the nodes that explicitly can't
> > > cope are factored out before we even get to cpuset constraints (plus this
> > > gives us a hook for setting up the interleave nodes in both the system
> > > init and default policies). Thoughts?
> >
> > I guess I don't understand which nodes you're talking about now? How
> > do you spread across any particular single node (how I read "Some
> > nodes are never going to tolerate spreading of any sort")? Or do you
> > mean that some cpusets aren't going to want to spread (interleave?).
> >
> > Oh, are you trying to say that some nodes should be dropped from
> > interleave masks (explicitly excluded from all possible interleave
> > masks)? What kind of nodes would these be? We're doing something
> > similar to deal with memoryless nodes, perhaps it could be
> > generalized?
>
> If that's what Paul means [and I think it is, based on a converstation
> at OLS], I have a similar requirement.  I'd like to be able to specify,
> on the command line, at least [run time reconfig not a hard requirement]
> nodes to be excluded from interleave masks, including the hugetlb
> allocation mask [if this is different from the regular interleaving
> nodemask].

Right this would avoid using that DMA node for your systems.

> And, I agree, I think we can add another node_states[] entry or two to
> hold these nodes.  I'll try to work up a patch next week if noone beats
> me to it.

Sounds good. I think the commandline interface might be a bit hairy --
but I'll leave that to you :)

So then, I'd say, by default the interleave masks should be and'd with
this node_states(N_INTERLEAVE), where if not otherwise specified,
node_states(N_INTERLEAVE) == node_states[N_MEMORY]?

Thanks,
Nish

--
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>

  reply	other threads:[~2007-07-20 21:12 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-13 15:16 [PATCH 0/5] [RFC] Dynamic hugetlb pool resizing Adam Litke
2007-07-13 15:16 ` [PATCH 1/5] [hugetlb] Introduce BASE_PAGES_PER_HPAGE constant Adam Litke
2007-07-23 19:43   ` Christoph Lameter
2007-07-23 19:52     ` Adam Litke
2007-07-13 15:16 ` [PATCH 2/5] [hugetlb] Account for hugepages as locked_vm Adam Litke
2007-07-13 15:16 ` [PATCH 3/5] [hugetlb] Move update_and_free_page so it can be used by alloc functions Adam Litke
2007-07-13 15:17 ` [PATCH 4/5] [hugetlb] Try to grow pool on alloc_huge_page failure Adam Litke
2007-07-13 15:17 ` [PATCH 5/5] [hugetlb] Try to grow pool for MAP_SHARED mappings Adam Litke
2007-07-13 20:05   ` Paul Jackson
2007-07-13 21:05     ` Adam Litke
2007-07-13 21:24       ` Ken Chen
2007-07-13 21:29       ` Christoph Lameter
2007-07-13 21:38         ` Ken Chen
2007-07-13 21:47           ` Christoph Lameter
2007-07-13 22:21           ` Paul Jackson
2007-07-13 21:38       ` Paul Jackson
2007-07-17 23:42         ` Nish Aravamudan
2007-07-18 14:44           ` Lee Schermerhorn
2007-07-18 15:17             ` Nish Aravamudan
2007-07-18 16:02               ` Lee Schermerhorn
2007-07-18 21:16                 ` Nish Aravamudan
2007-07-18 21:40                   ` Lee Schermerhorn
2007-07-19  1:52                 ` Paul Mundt
2007-07-20 20:35                   ` Nish Aravamudan
2007-07-20 20:53                     ` Lee Schermerhorn
2007-07-20 21:12                       ` Nish Aravamudan [this message]
2007-07-21 16:57                     ` Paul Mundt
2007-07-13 23:15       ` Nish Aravamudan
2007-07-13 21:09     ` Ken Chen

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=29495f1d0707201412y29329807v33cdf1854ade9928@mail.gmail.com \
    --to=nish.aravamudan@gmail.com \
    --cc=Lee.Schermerhorn@hp.com \
    --cc=agl@us.ibm.com \
    --cc=apw@shadowen.org \
    --cc=clameter@sgi.com \
    --cc=kenchen@google.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@skynet.ie \
    --cc=pj@sgi.com \
    --cc=wli@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox