lkml.org 
[lkml]   [2008]   [May]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: MMIO and gcc re-ordering issue


On Tue, 27 May 2008, Alan Cox wrote:
>
> > re-ordering, even though I doubt it will be visible in practice. So if you
> > use the "__" versions, you'd better have barriers even on x86!
>
> Are we also going to have __ioread*/__iowrite* ?

I doubt there is any reason to. Let's just keep them very strictly
ordered.

> Also is the sematics of __readl/__writel defined for all architectures -
> I used it ages ago in the i2o drivers for speed and it got removed
> because it didn't build on some platforms.

Agreed - I'm not sure the __ versions are really worth it. We have them,
but the semantics are subtle enough that most drivers will never care
enough to really use them.

I would suggest using them mainly for architecture-specific drivers, on
architectures where it actually matters (which is not the case on x86).

Linus


\
 
 \ /
  Last update: 2008-05-28 00:03    [from the cache]
©2003-2014 Jasper Spaans. Advertise on this site