linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Leandro Motta Barros <lmb@exatas.unisinos.br>
To: linux-mm@kvack.org
Cc: sisopiii-l@cscience.org
Subject: Freeing boot memory
Date: Tue, 16 Sep 2003 18:17:37 -0300	[thread overview]
Message-ID: <200309161817.37802.lmb@exatas.unisinos.br> (raw)

Hello,

I and a colleague are studying the VM subsystem (actually this is the first 
time we are examining the Linux source code more closely) and have a question 
or two.

Well, the questions concern the boot memory allocator. To be more precise, 
We're interested in the memory deallocation routines. We have seen that it is 
only possible to free full pages. So, theoretically, if we make several 
allocations smaller than one page, we will not be able to actually free this 
memory. I just don't know of this kind of situation happens in real life. Do 
we currently have some pages of memory "wasted" because the boot memory 
allocator was not able to free small allocations? Is there any estimate (or 
benchmark or whatever) on the number of pages that could be freed but are 
not?

We have interest in hacking a little bit in the VM, and we thought that trying 
to find out ways to avoid this problem (if this is really a problem) could be 
nice. Do you have any thoughts about this?

Thanks a lot,

LMB
--
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:"aart@kvack.org"> aart@kvack.org </a>

             reply	other threads:[~2003-09-16 21:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-16 21:17 Leandro Motta Barros [this message]
2003-09-16 21:17 ` Martin J. Bligh
2003-09-16 21:34 ` William Lee Irwin III

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=200309161817.37802.lmb@exatas.unisinos.br \
    --to=lmb@exatas.unisinos.br \
    --cc=linux-mm@kvack.org \
    --cc=sisopiii-l@cscience.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