Intel's "cripple AMD" function

Re:Intel's "cripple AMD" function by ars on Sunday January 03, 2010 @02:37PM (#1028955)

Size does affect performance because of the cache.

If the forks are inline, and the cache works in blocks, then you are wasting cache space for code that never runs.

But considering it's intel I'm sure they thought of that.

[ Parent | on HN ]

Re:Intel's "cripple AMD" function by pmjordan on Sunday January 03, 2010 @04:09PM (#1029142)

I suspect it patches a jumptable at initialisation time based on CPU type, and all the code used by one type of CPU is bunched close together. The unused code probably isn't even paged into physical RAM.

[ Parent | on HN ]

Re:Intel's "cripple AMD" function by DougBTX on Sunday January 03, 2010 @04:11PM (#1029147)

Certainly. These are performance optimisations, they must measure results.

[ Parent | on HN ]