mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Muthian Sivathanu <muthian_s@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: isolated memory pools ?
Date: Wed, 14 May 2003 09:35:58 -0700 (PDT)	[thread overview]
Message-ID: <20030514163558.56819.qmail@web40611.mail.yahoo.com> (raw)

Hi,

Does anyone know if there is a simple way to manage
isolated memory pools in linux ?  I am writing a
device driver that does a lot of memory allocation to
keep track of some internal data structures. However,
when the system is subjected to an I/O intensive
workload for instance, the file system cache takes
away a lot of memory, leading to unpredictable delays
in memory allocation within my driver, which creates a
lot of performance problems.

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 ?

Thanks,
Muthian.

P.S: Please CC my personal address in your replies
since I am not a member of
the mailing list.


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

             reply	other threads:[~2003-05-14 16:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14 16:35 Muthian Sivathanu [this message]
2003-05-15 15:58 ` Ingo Oeser
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=20030514163558.56819.qmail@web40611.mail.yahoo.com \
    --to=muthian_s@yahoo.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®