KUROSAWA Takahiro wrote:
It looks you don't want to use functions based on zones, buddy-system, lru-list
etc..
I think what you want is just a hierarchical memory allocator.
Why do you modify zone and make codes complicated ?
Can your memory allocater be implimented like mempool or hugetlb ?
They are not so invasive.
mempool and hugetlb require their own shrinking code, don't they?
I guess that we would need the routines like mm/vmscan.c if we are
going to shrink user pages. Instead, I'd like to reuse the shrinking
code in mm/vmscan.c.
I think you can reuse shrink_list() at least.
Code duplication you're afraid of can be small.
I think call shrink_list() from your own shrinking fuction will add
good control on CKRM's memory region.
-- Kame
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
ckrm-tech mailing list
https://lists.sourceforge.net/lists/listinfo/ckrm-tech
