ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Daniel Phillips <d.phillips@partner.samsung.com>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Redesign Memory Management layer and more core subsystem
Date: Wed, 11 Jun 2014 12:26:49 -0700	[thread overview]
Message-ID: <5398AD79.8080403@partner.samsung.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1406111336240.9616@gentwo.org>

On 06/11/2014 12:03 PM, Christoph Lameter wrote:
> Well this is likely to be a bit of a hot subject but I have been thinking
> about this for a couple of years now. This is just a loose collection of
> some concerns that I see mostly at the high end but many of these also are
> valid for more embedded solutions that have performance issues as well
> because the devices are low powered (Android?).
>
> There are numerous issues in memory management that create a level of
> complexity that suggests a rewrite would at some point be beneficial:
>
> 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
> linear memory where we have trouble and are creating numerous memory
> allocators (recently the new bootmem allocator and CMA. Plus lots of
> specialized allocators in various subsystems).
>
>

mem_map should be a radix tree?

Regards,

Daniel

  reply	other threads:[~2014-06-11 19:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11 19:03 Christoph Lameter
2014-06-11 19:26 ` Daniel Phillips [this message]
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
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=5398AD79.8080403@partner.samsung.com \
    --to=d.phillips@partner.samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox