* Anybody interested in a kernel memory manager?
@ 2008-10-02 5:54 Gregor Rebel
2008-10-02 9:49 ` Gregor Rebel
2008-10-02 16:58 ` Jeremy Fitzhardinge
0 siblings, 2 replies; 3+ messages in thread
From: Gregor Rebel @ 2008-10-02 5:54 UTC (permalink / raw)
To: linux-kernel
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Anybody interested in a kernel memory manager?
2008-10-02 5:54 Anybody interested in a kernel memory manager? Gregor Rebel
@ 2008-10-02 9:49 ` Gregor Rebel
2008-10-02 16:58 ` Jeremy Fitzhardinge
1 sibling, 0 replies; 3+ messages in thread
From: Gregor Rebel @ 2008-10-02 9:49 UTC (permalink / raw)
To: linux-kernel
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/
>
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Anybody interested in a kernel memory manager?
2008-10-02 5:54 Anybody interested in a kernel memory manager? Gregor Rebel
2008-10-02 9:49 ` Gregor Rebel
@ 2008-10-02 16:58 ` Jeremy Fitzhardinge
1 sibling, 0 replies; 3+ messages in thread
From: Jeremy Fitzhardinge @ 2008-10-02 16:58 UTC (permalink / raw)
To: Gregor Rebel; +Cc: linux-kernel
Gregor Rebel wrote:
> I'm currently writing two modules related to XEN.
What are you working on, out of curiosity?
> 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?
The best way to get a useful response is to post the patches and see
what happens. There's no way to really evaluate what you're proposing
in the abstract.
J
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-10-02 16:58 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-10-02 5:54 Anybody interested in a kernel memory manager? Gregor Rebel
2008-10-02 9:49 ` Gregor Rebel
2008-10-02 16:58 ` Jeremy Fitzhardinge
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox