login
Header Space

 
 

Re: x86 merge - a little feedback

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Sam Ravnborg <sam@...>
Cc: Thomas Gleixner <tglx@...>, Ingo Molnar <mingo@...>, Andi Kleen <ak@...>, LKML <linux-kernel@...>
Date: Tuesday, September 11, 2007 - 5:21 pm

On Tue, 11 Sep 2007, Sam Ravnborg wrote:

The problem right now is the *reverse* - even though they are in different 
subdirectories (and thus *look* like they are all separate), they aren't.

So the merged end result is much better: at a first approximation 
everything is shared (largely true), and the ones that aren't shared can 
be made more obvious.


So sharing is the default, as it should be.


And these are examples of things that likely *should* be shared, and have 
nothing what-so-ever to do with 32- vs 64-bit issues. For example, neither 
NUMA nor k8 is in *any* way a 32-bit vs 64-bit issue, they are issues with 
chips that can be used as either.


And this is obvious, and correct.


Now, arguably this should be entirely elsewhere (ie in the "mach-visw" 
directory).


.. and that's because of historical issues, and has nothing to do with the 
merge, and everything to do with all the problems that the merge is 
supposed to eventually help us FIX!


Yes. But so are others.


But none of it is "i386 only" and putting it in a directory of its own 
would be stupid and wrong. The visws.c thing is platform-specific thing, 
and the fact that the platform happens to be 32-bit is totally secondary 
to the much bigger issue of the *platform*, so again, it would be totally 
wrong to split it up by wordsize.


I obviously disagree violently. We should absolutely *not* make any of 
this depend on word-size. Quite the reverse!

		Linus
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
x86 merge - a little feedback, Sam Ravnborg, (Tue Sep 11, 4:12 pm)
Re: x86 merge - a little feedback, Linus Torvalds, (Tue Sep 11, 5:21 pm)
Re: x86 merge - a little feedback, Sam Ravnborg, (Wed Sep 12, 3:09 pm)
Re: x86 merge - a little feedback, Andi Kleen, (Tue Sep 11, 4:38 pm)
Re: x86 merge - a little feedback, Adrian Bunk, (Tue Sep 11, 5:14 pm)
Re: x86 merge - a little feedback, Andrew Morton, (Sat Sep 15, 5:32 am)
Re: x86 merge - a little feedback, Andi Kleen, (Sat Sep 15, 2:36 pm)
Re: x86 merge - a little feedback, Andrew Morton, (Sun Sep 16, 1:08 am)
Re: x86 merge - a little feedback, Andi Kleen, (Tue Sep 11, 5:34 pm)
Re: x86 merge - a little feedback, Paul Mundt, (Tue Sep 11, 8:29 pm)
Re: x86 merge - a little feedback, Andrew Morton, (Sat Sep 15, 6:55 am)
Re: x86 merge - a little feedback, Linus Torvalds, (Tue Sep 11, 5:51 pm)
Re: x86 merge - a little feedback, Jan Engelhardt, (Wed Sep 12, 2:14 pm)
Re: x86 merge - a little feedback, Adrian Bunk, (Tue Sep 11, 5:51 pm)
Re: x86 merge - a little feedback, Adrian Bunk, (Tue Sep 11, 4:34 pm)
Re: x86 merge - a little feedback, Christoph Hellwig, (Wed Sep 12, 5:27 am)
Re: x86 merge - a little feedback, Lennart Sorensen, (Wed Sep 12, 8:45 am)
Re: x86 merge - a little feedback, Sam Ravnborg, (Tue Sep 11, 5:05 pm)
Re: x86 merge - a little feedback, Adrian Bunk, (Tue Sep 11, 5:09 pm)
Re: x86 merge - a little feedback, Thomas Gleixner, (Tue Sep 11, 4:25 pm)
Re: x86 merge - a little feedback, Linus Torvalds, (Tue Sep 11, 5:24 pm)
speck-geostationary