Re: /proc/cpuinfo format - arch dependent!

[Chris Friesen]

Bill Davidsen wrote:

> Might I suggest that if you like the "we know best just trust us" 
> approach, there is another OS to use. Making information available to 
> good applications will improve system performance, or at least allow 
> better limitation of requests for resources

What will you do with the information?  The kernel is doing all the 
resource allocation and scheduling.

From a higher-level, the application wants the best performance. 
Doesn't it make more sense to have an API that lets you query things 
like: how many cores do I have, how many separate memory interfaces do I 
have, how many cores handle interrupts, etc.

Based on that information you tell the system: "I've got 4 processes, 
please put them all on cores with separate memory connectivity since 
they're all memory-intensive. Now please put these other two threads on 
the same cpu since they share memory but serialize each other by design."

The app shouldn't care about the details of architecture, but it should 
be able to work with the system to give the best performance.

Chris
-
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/