[lkml]   [1999]   [Aug]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: New resources - pls, explain :-(
> (I exaggerate.  Alan Cox said that not reordering was a safer default
> (which is essentially my position) and Dave Miller said to me in
> private email something along the lines that any sane architecture has
> a side-effect bit in the PTEs to prevent reordering of accesses to
> certain pages.)

How many insane architectures are there in the world though.

> this: ncr, aic7xxx, tulip, epic100. How many others would there be in
> this category? It sounds to me like the vast majority of drivers
> which use readl/writel would be assuming that they prevent reordering.

I think that is fairly accurate.

> My position is that readl/writel should prevent reordering (of the
> accesses generated by read*/write*), and that we should have variants,
> maybe called readl_fast etc., for the cases where performance is
> crucial and the driver writer is willing to put in explicit barriers
> where necessary.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:53    [W:0.085 / U:4.044 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site