All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregor Rebel <linux@mailbarrier.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Anybody interested in a kernel memory manager?
Date: Thu, 02 Oct 2008 11:49:34 +0200	[thread overview]
Message-ID: <48E4992E.6030102@mailbarrier.de> (raw)
In-Reply-To: <48E46214.2090108@mailbarrier.de>

Hi again,

maybe the name is misleading, a better would could be kernel resource 
tracker.

--
Gregor
> Hi,
>
> I'm currently writing two modules related to XEN. Both modules need to
> acquire dynamic memory (via __get_free_pages() and kmalloc() ).
> In order to reuse some code, I wrote a third module which can provide
> simple memory-services to other modules:
> * Allocated pages and memories of each client-module gets tracked
> * When a module is about to exit, it can issue one function call to
> release all of its memories
> * Before first using the memory manager, each module has to obtain a
> unique owner id number by calling a registration function
> * by loading the memory manager with a debug argument, memory
> allocations automatically get logged into syslog facility
>
> I know, that currently each module keeps track of its memory allocations
> on its own.
>
> Is there a general interest to have such a memory manager in the kernel?
>
>
> -- 
> Gregor
>
> -- 
> 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/
>
>


  reply	other threads:[~2008-10-02  9:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02  5:54 Anybody interested in a kernel memory manager? Gregor Rebel
2008-10-02  9:49 ` Gregor Rebel [this message]
2008-10-02 16:58 ` Jeremy Fitzhardinge

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=48E4992E.6030102@mailbarrier.de \
    --to=linux@mailbarrier.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.