From: "Michał Nazarewicz" <m.nazarewicz@samsung.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, m.szyprowski@samsung.com,
kyungmin.park@samsung.com, linux-mm@kvack.org
Subject: Re: [PATCH] Physical Memory Management [0/1]
Date: Fri, 15 May 2009 14:05:17 +0200 [thread overview]
Message-ID: <op.utyzu3ot7p4s8u@amdc030> (raw)
In-Reply-To: <20090515112656.GD16682@one.firstfloor.org>
>> On Fri, 15 May 2009 12:18:11 +0200, Andi Kleen wrote:
>>> However for non fragmentation purposes you probably don't
>>> want too many different sizes anyways, the more sizes, the worse
>>> the fragmentation. Ideal is only a single size.
> On Fri, May 15, 2009 at 12:47:23PM +0200, MichaA? Nazarewicz wrote:
>> Unfortunately, sizes may very from several KiBs to a few MiBs.
On Fri, 15 May 2009 13:26:56 +0200, Andi Kleen <andi@firstfloor.org> wrote:
> Then your approach will likely not be reliable.
>> On the other hand, only a handful of apps will use PMM in our system
>> and at most two or three will be run at the same time so hopefully
>> fragmentation won't be so bad. But yes, I admit it is a concern.
>
> Such tight restrictions might work for you, but for mainline Linux the
> quality standards are higher.
I understand PMM in current form may be unacceptable, however, hear me
out and please do correct me if I'm wrong at any point as I would love
to use an existing solution if any fulfilling my needs is present:
When different sizes of buffers are needed fragmentation is even bigger
problem in hugetlb (as pages must be aligned) then with PMM.
If a buffer that does not match page size is needed then with hugetlb
either bigger page needs to be allocated (and memory wasted) or few
smaller need to be merged (and the same problem as in PMM exists --
finding contiguous pages).
Reclaiming is not really an option since situation where there is no
sane bound time for allocation is not acceptable -- you don't want to
wait 10 seconds for an application to start on your cell phone. ;)
Also, I need an ability to convert any buffer to a Sys V shm, as to
be able to pass it to X server. Currently no such API exist, does it?
With PMM and it's notion of memory types, different allocators and/or
memory pools, etc. Allocators could be even dynamically loaded as
modules if one desires that. My point is, that PMM is to be considered
a framework for situations similar to the one I described thorough all
of my mails, rather then a universal solution.
--
Best regards, _ _
.o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o
..o | Computer Science, MichaA? "mina86" Nazarewicz (o o)
ooo +-<m.nazarewicz@samsung.com>-<mina86@jabber.org>-ooO--(_)--Ooo--
--
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>
next prev parent reply other threads:[~2009-05-15 12:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <op.utu26hq77p4s8u@amdc030>
2009-05-13 22:11 ` Andrew Morton
2009-05-14 9:00 ` Michał Nazarewicz
2009-05-14 11:20 ` Peter Zijlstra
2009-05-14 11:48 ` Michał Nazarewicz
2009-05-14 12:05 ` Peter Zijlstra
2009-05-14 13:04 ` Michał Nazarewicz
2009-05-14 17:07 ` Andrew Morton
2009-05-14 17:10 ` Peter Zijlstra
2009-05-15 10:06 ` Michał Nazarewicz
2009-05-15 10:18 ` Andi Kleen
2009-05-15 10:47 ` Michał Nazarewicz
2009-05-15 11:03 ` Peter Zijlstra
2009-05-15 11:11 ` Michał Nazarewicz
2009-05-15 11:26 ` Andi Kleen
2009-05-15 12:05 ` Michał Nazarewicz [this message]
2009-05-14 19:33 ` Andi Kleen
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=op.utyzu3ot7p4s8u@amdc030 \
--to=m.nazarewicz@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=peterz@infradead.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