![]() | ||||||||||
Messages in this thread |
Andrew Morton wrote: >But different filesystems will leave different amounts of dirty, unwritten >data in memory at the end of the test. On your machine, up to 200MB of >dirty data could be sitting there in memory at the end of the timing >interval. You need to decide how to account for that unwritten data in the >measurement. Simply ignoring it as you have done is certainly valid, but >is only realistic in a couple of scenarios: > unless I misunderstand something, he is running sync and not ignoring that. I don't think ext2 is a serious option for servers of the sort that Linux specializes in, which is probably why he didn't measure it. reiser4 cpu consumption is still dropping rapidly as others and I find kruft in the code and remove it. Major kruft remains still. -- Hans - 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/ | |||||||||
| Last update: 2005-03-22 12:47 [from the cache] ©2003-2008 | ||||||||||