From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Paul Mundt <lethal@linux-sh.org>,
Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH 15/35] x86, lmb: Add lmb_reserve_area_overlap_ok()
Date: Tue, 15 Jun 2010 16:55:43 +1000 [thread overview]
Message-ID: <1276584943.2552.99.camel@pasglop> (raw)
In-Reply-To: <4C16C928.2000406@kernel.org>
On Mon, 2010-06-14 at 17:28 -0700, Yinghai Lu wrote:
> On 06/04/2010 06:47 PM, Benjamin Herrenschmidt wrote:
> > On Fri, 2010-06-04 at 18:35 -0700, Yinghai Lu wrote:
> ..
> >> can you rebase powerpc/lmb, so we can put lmb for x86 changes to tip
> >> and next?
> >
> > I will. I've been kept busy with all sort of emergencies and the merge
> > window, but I will do that and a could of other things to it some time
> > next week.
>
> Ping!
(Adding back the list)
I've updated the series (*) It's just a rebase from the previous one,
and one change: I don't allow resizing until after lmb_analyze() has run
since on various platforms, doing it too early such as when constructing
the memory array is risky as we haven't done the necessary lmb_reserve()
of whatever regions are unsuitable for allocation.
We can improve on that later, maybe by doing those reservations early,
before we add memory, or whatever, but that can wait.
Yinghai, is there any other chance you want me to do to the core ?
Another thing to add at some stage for ARM will be a default alloc base
in addition to limit, that constraints "standard" allocations.
(*) Usual place:
git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc.git lmb
Cheers,
Ben.
--
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>
parent reply other threads:[~2010-06-15 6:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4C16C928.2000406@kernel.org>]
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=1276584943.2552.99.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=hpa@zytor.com \
--cc=lethal@linux-sh.org \
--cc=linux-mm@kvack.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai@kernel.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;
as well as URLs for NNTP newsgroup(s).