mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Muthian Sivathanu <muthian_s@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: isolated memory pools ?
Date: Thu, 15 May 2003 17:58:34 +0200	[thread overview]
Message-ID: <20030515175834.A626@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20030514163558.56819.qmail@web40611.mail.yahoo.com>; from muthian_s@yahoo.com on Wed, May 14, 2003 at 09:35:58AM -0700

Hi Muthian,

On Wed, May 14, 2003 at 09:35:58AM -0700, Muthian Sivathanu wrote:
> Ideally, I would like to be able to allocate my own
> memory pool, say, with 10% of the host memory, and
> then have total control over it, i.e. the rest of the
> kernel should not allocate from this space, and my
> local free_pages should return memory back to my local
> pool.  One obvious way to do this would be to pin
> those pages to memory and then write my own memory
> management routines to handle allocations within the
> pool, but that seems time consuming and hard.  Is
> there a way the existing kernel memory management
> routines can be harnessed to manage
> such an isolated free pool ?

#include <linux/mempool.h>

and look at the functions, which implement this.

linux/mm/mempool.c is the actual implementation.

This is not exactly, what you want (you CAN allocate more than
your 10% from this pool and the amount over your minimum number
of pages to be reserved is free for the kernel to use), but
should be what you really need.

Regards

Ingo Oeser


  reply	other threads:[~2003-05-15 16:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14 16:35 Muthian Sivathanu
2003-05-15 15:58 ` Ingo Oeser [this message]
2003-05-15 19:35   ` Muthian Sivathanu

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=20030515175834.A626@nightmaster.csn.tu-chemnitz.de \
    --to=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muthian_s@yahoo.com \
    /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

all inboxes | Powered by JetHome®