From: Rik van Riel <riel@redhat.com>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Redesign Memory Management layer and more core subsystem
Date: Fri, 13 Jun 2014 18:23:03 -0400 [thread overview]
Message-ID: <539B79C7.5090506@redhat.com> (raw)
In-Reply-To: <1402695366.20360.14.camel@pasglop>
On 06/13/2014 05:36 PM, Benjamin Herrenschmidt wrote:
> On Fri, 2014-06-13 at 12:02 -0500, Christoph Lameter wrote:
>> On Thu, 12 Jun 2014, Phillip Lougher wrote:
>>
>>>> 1. The need to use larger order pages, and the resulting problems with
>>>> fragmentation. Memory sizes grow and therefore the number of page structs
>>>> where state has to be maintained. Maybe there is something different? If
>>>> we use hugepages then we have 511 useless page structs. Some apps need
>> It is solvable if the objects are inherent movable. If any object
>> allocated provides a function that makes an object movable then
>> defragmentation is possible and therefore large contiguous area of memory
>> can be created at any time.
>
> Another interesting thing is migration of pages with mapped DMA on
> them :-)
>
> Our IOMMUs support that, but there isn't a way to hook that up into
> Linux page migration that wouldn't suck massively at this point.
The HMM stuff Jerome Glisse is working on may be a suitable
framework to add call callbacks for things like migration to.
--
All rights reversed
next prev parent reply other threads:[~2014-06-13 22:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 19:03 [Ksummit-discuss] [CORE TOPIC] Redesign Memory Management layer and more core subsystem Christoph Lameter
2014-06-11 19:26 ` Daniel Phillips
2014-06-11 19:45 ` Greg KH
2014-06-12 13:35 ` John W. Linville
2014-06-13 16:57 ` Christoph Lameter
2014-06-13 17:31 ` Greg KH
2014-06-13 17:59 ` Christoph Lameter
2014-06-13 19:18 ` Stephen Hemminger
2014-06-13 22:30 ` Christoph Lameter
2014-06-13 16:56 ` Christoph Lameter
2014-06-13 17:30 ` Greg KH
2014-06-13 17:55 ` James Bottomley
2014-06-13 18:41 ` Christoph Lameter
2014-06-16 11:39 ` Thomas Petazzoni
2014-06-16 14:05 ` Christoph Lameter
2014-06-16 14:09 ` Thomas Petazzoni
2014-06-16 14:28 ` Christoph Lameter
2014-06-13 18:01 ` Christoph Lameter
2014-06-13 18:25 ` Greg KH
2014-06-13 18:54 ` Christoph Lameter
2014-06-11 20:08 ` josh
2014-06-11 20:15 ` Andy Lutomirski
2014-06-11 20:52 ` Dave Hansen
2014-06-12 6:59 ` Phillip Lougher
2014-06-13 17:02 ` Christoph Lameter
2014-06-13 21:36 ` Benjamin Herrenschmidt
2014-06-13 22:23 ` Rik van Riel [this message]
2014-06-13 23:04 ` Christoph Lameter
2014-06-14 1:19 ` Phillip Lougher
2014-06-16 14:04 ` Christoph Lameter
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=539B79C7.5090506@redhat.com \
--to=riel@redhat.com \
--cc=ksummit-discuss@lists.linuxfoundation.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.