linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Larry Bassel <lbassel@codeaurora.org>
To: mgorman@suse.de
Cc: dan.magenheimer@oracle.com, linux-mm@kvack.org
Subject: steering allocations to particular parts of memory
Date: Fri, 7 Sep 2012 11:27:15 -0700	[thread overview]
Message-ID: <20120907182715.GB4018@labbmf01-linux.qualcomm.com> (raw)

I am looking for a way to steer allocations (these may be
by either userspace or the kernel) to or away from particular
ranges of memory. The reason for this is that some parts of
memory are different from others (i.e. some memory may be
faster/slower). For instance there may be 500M of "fast"
memory and 1500M of "slower" memory on a 2G platform.

At the memory mini-summit last week, it was mentioned
that the Super-H architecture was using NUMA for this
purpose, which was considered to be an very bad thing
to do -- we have ported NUMA to ARM here (as an experiment)
and agree that NUMA doesn't work well for solving this problem.

After the NUMA discussion, I spoke briefly to you and asked
you what a good approach would be. You thought that something
based on transcendent memory (which I am somewhat familiar
with, having built something based upon it which can be used either
as contiguous memory or as clean cache) might work, but
you didn't supply any details.

At the time, you asked me to email you about this and copy
Dan and the linux-mm mailing list, where hopefully you or Dan
might be able to explain how this would work.

Thanks.

Larry Bassel

-- 
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

--
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:[~2012-09-07 18:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07 18:27 Larry Bassel [this message]
2012-09-11  9:34 ` Mel Gorman
2012-09-12 21:28   ` Larry Bassel
2012-09-13  8:34     ` Mel Gorman
2012-09-17 19:40       ` Dan Magenheimer
2012-09-18  8:32         ` Mel Gorman
2012-09-21 17:44         ` Larry Bassel

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=20120907182715.GB4018@labbmf01-linux.qualcomm.com \
    --to=lbassel@codeaurora.org \
    --cc=dan.magenheimer@oracle.com \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    /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