Date: Thu, 15 May 2003 17:58:34 +0200
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 ?
Message-ID: <20030515175834.A626@nightmaster.csn.tu-chemnitz.de>
References: <20030514163558.56819.qmail@web40611.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
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
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1300
Lines: 36

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/