Re: [Lhms-devel] Re: [PATCH 0/5] Reducing fragmentation using zones

From: KAMEZAWA Hiroyuki
Date: Thu Jan 19 2006 - 19:15:08 EST


Joel Schopp wrote:
Benchmark comparison between -mm+NoOOM tree and with the new zones

I know you had also previously posted a very simplified version of your real fragmentation avoidance patches. I was curious if you could repost those with the other benchmarks for a 3 way comparison. The simplified version got rid of a lot of the complexity people were complaining about and in my mind still seems like preferable direction.

I agree. I think you should try with simplified version again.
Then, we can discuss.

I don't like using bitmap which I removed (T.T

Zone based approaches are runtime inflexible and require boot time tuning by the sysadmin. There are lots of workloads that "reasonable" defaults for a zone based approach would cause the system to regress terribly.

IMHO, I don't like automatic runtime tuning, you say 'flexible' here.
I think flexibility allows 2^(MAX_ORDER - 1) size fragmentaion.
When SECTION_SIZE > MAX_ORDER, this is terrible.

I love certainty that sysadmin can grap his system at boot-time.
And, for people who want to remove range of memory, list-based approach will
need some other hook and its flexibility is of no use.
(If list-based approach goes, I or someone will do.)

I know zone->zone_start_pfn can be removed very easily.
This means there is possiblity to reconfigure zone on demand and
zone-based approach can be a bit more fliexible.


- Kame

-Joel


-------------------------------------------------------
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
_______________________________________________
Lhms-devel mailing list
Lhms-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/lhms-devel



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/