[lkml]   [2008]   [Apr]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH]: Fix SMP-reordering race in mark_buffer_dirty

On Wed, 2 Apr 2008, Linus Torvalds wrote:

> On Wed, 2 Apr 2008, Andrew Morton wrote:
> >
> > But then the test-and-set of an already-set flag would newly cause the
> > cacheline to be dirtied, requiring additional bus usage to write it back?
> >
> > The CPU's test-and-set-bit operation could of course optimise that away in
> > this case. But does it?
> No, afaik no current x86 uarch will optimize away the write on a locked
> instuction if it turns out to be unnecessary.

No, it doesn't. Try this:

#include <string.h>
#include <pthread.h>
void *pth(void *p)
int i;
for (i = 0; i < 100000000; i++)
__asm__ volatile ("lock;btsl $0, %0"::"m"(*(int
return NULL;
int args[2000];
int main(void)
pthread_t t1, t2, t3, t4;
memset(args, -1, sizeof args);
pthread_create(&t1, NULL, pth, &args[0]);
pthread_create(&t2, NULL, pth, &args[16]);
pthread_create(&t3, NULL, pth, &args[32]);
pthread_create(&t4, NULL, pth, &args[48]);
pthread_join(t1, NULL);
pthread_join(t2, NULL);
pthread_join(t3, NULL);
pthread_join(t4, NULL);
return 0;

--- when the &args[] indices are in a conflicting cacheline, I get 9 times
slower execution. I tried it on 2 double-core Core 2 Xeons.


> Can somebody find a timing reason to have the ugly code?
> Linus

 \ /
  Last update: 2008-04-03 00:55    [W:0.048 / U:2.448 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site