Skip to contentSkip to conversation

Anybody interested in a kernel memory manager?

DISCUSSION Gregor Rebel 2 participants 3 messages Oct 2, 2008

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw

Hi again,

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

--
Gregor

Quoted 30 lines

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?

Signature · 7 lines
Gregor

-- 
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
#2 lore raw
In reply to Gregor Rebel
Quoted 1 line · Gregor Rebel

I'm currently writing two modules related to XEN.

What are you working on, out of curiosity?

Quoted 12 lines

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

Quoted 4 lines

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