HT scheduler
A message that is not in the archive (sent off-list or not yet received): 20031213022038.300B22C2C1@lists.samba.org.suse.lists.linux.kernel
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 20031214043245.GC21241@mail.shareable.org.suse.lists.linux.kernel
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 1071398761.5233.1.camel@laptop.fenrus.com.suse.lists.linux.kernel
Quoted 4 lines · Arjan van de Ven
also keep in mind that current x86 processors all will internally optimize out the lock prefix in UP mode or when the cacheline is owned exclusive.... If HT matters here let the cpu optimize it out.....
Are you sure they optimize it out in UP mode? IMHO this would break device drivers that use locked cycles to communicate with bus master devices (and which are not necessarily mapped uncachable/write combining)
-Andi
Quoted 9 lines · Andi Kleen
Quoted 4 lines · Arjan van de Ven
also keep in mind that current x86 processors all will internally optimize out the lock prefix in UP mode or when the cacheline is owned exclusive.... If HT matters here let the cpu optimize it out.....
Are you sure they optimize it out in UP mode? IMHO this would break device drivers that use locked cycles to communicate with bus master devices (and which are not necessarily mapped uncachable/write combining)
uncachable regions are different obviously....