[lkml]   [2010]   [Sep]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: memory barrier question

> Right but in the concrete namei example I can't see how a compiler
> optimization can make a difference. The order of the loads is quite
> clear:
> LOAD inode = next.dentry->inode
> if (inode != NULL)
> LOAD inode->f_op
> What is there the compiler can optimize?

Those two loads depend on each other, I don't think any implementation
can re-order them. In fact, such data dependency is typically what is
used to avoid having barriers in some cases. The second load cannot be
issued until the value from the first one is returned.


 \ /
  Last update: 2010-09-17 23:53    [W:0.085 / U:17.140 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site