On Fri, 2002-08-02 at 16:46, Linus Torvalds wrote:
> Personally, I would just say that we should disable prefetch on such
> clearly broken hardware, but since it's Alans favourite machine (some
> early AMD Athlon if I remember correctly), I think Alan will disagree ;)
Its an expensive change. I'm also not convinced the AMD is the only
situation this comes up. And however you look at it, fetching memory you
don't need is a bug. You are not just wasting memory bandwidth, which
you may have on ia64 but not so much on real computers, you are pulling
stuff shared on other processors which can be quite expensive.
The guarantee I specced in the original API was specifically that
prefetching a NULL pointer was safe.
> That's true of just about any other architecture too. I think the AMD case
> is an erratum, so even on AMD it is _supposed_ to work.
Nothing guarantees a page adjacent to the user memory is not cachable. I
can't think of anything cachable with nasty side effects we might
encounter right now but one day someone will do it just to be annoying.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Aug 07 2002 - 22:00:19 EST