linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: linux-mm@kvack.org
Cc: David Woodhouse <dwmw2@infradead.org>,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/2] allow bootmem to be freed to allocator late
Date: Fri, 23 Oct 2009 10:10:51 -0700	[thread overview]
Message-ID: <20091023171051.993073846@sequoia.sous-sol.org> (raw)

Currently there is no way to release bootmem once the bootmem allocator
frees all unreserved memory.  This adds the ability to free reserved
pages directly to the page allocator after the bootmem allocator metadata
is already freed.  It's limited in scope since it's still all marked
__init, and creates a new entry point free_bootmem_late rather than
trying to do this automatically in free_bootmem.  Hence the RFC...

With this we are able to do something like allocate swiotlb, and then
free it later if we discover we had a hw iommu that doesn't need swiotlb.

 include/linux/bootmem.h |    1 +
 mm/bootmem.c            |   98 ++++++++++++++++++++++++++++++++++++----------
 2 files changed, 77 insertions(+), 22 deletions(-)

thanks,
-chris

--
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>

             reply	other threads:[~2009-10-23 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-23 17:10 Chris Wright [this message]
2009-10-23 17:10 ` [RFC PATCH 1/2] bootmem: refactor free_all_bootmem_core Chris Wright
2009-10-23 17:10 ` [RFC PATCH 2/2] bootmem: add free_bootmem_late Chris Wright

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=20091023171051.993073846@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=dwmw2@infradead.org \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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).