From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de, mingo@elte.hu,
davem@davemloft.net, lethal@linux-sh.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: [PATCH/WIP] lmb cleanups and additions
Date: Mon, 10 May 2010 19:48:13 +1000 [thread overview]
Message-ID: <1273484893.23699.86.camel@pasglop> (raw)
(Resent that header email, git send-email is having hickups here)
This is my current WIP series. It's compile tested on ppc and sparc64 and
quickly boot tested on ppc64. The "advanced" features such as the new
array resize are completely untested in this version.
My aim is still to replace the bottom part of Yinghai's patch series
rather than build on top of it, and from there, add whatever he needs
to successfully port x86 over and turn NO_BOOTMEM into something half
decent without adding a ton of unneeded crap to the core lmb.
This is not finished tho. Here's a peek at my TODO list:
- Move to mm/lmb.c
- Various random return types with non-useful return codes (lmb_add, lmb_remove, ...)
needs cleaning & documenting
- Add docbook for all API functions
- lmb_add or lmb_reserve of overlapping regions are going to wreck things in very
interesting ways. We could easily error out but that's sub-optimal, instead we
should break them up to only add/reserve the bits that aren't yet
- Add some pr_debug in various places in there
- Improve the NUMA interaction
In the meantime, comments are welcome :-)
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>
next reply other threads:[~2010-05-10 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 9:48 Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-10 9:38 [PATCH/WIP] lmb cleanups and additions Benjamin Herrenschmidt
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=1273484893.23699.86.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).