sandpile.org -- discussion forum

discussion forum

message

Name:	86th Guru
Date:	June 10, 2003 at 12:23:59
Subject:	Re: Hyperthreading and 'lock' prefix
In Reply To:	Re: Hyperthreading and 'lock' prefix by Stephan Keil on June 10, 2003 at 09:09:36
Text:	`\| Both processors share the same pipeline. If the pipeline would care \| about read-modify-write conflicts regardless of the executing \| thread (as it does for a single thread), then it would be safe to omit \| the 'lock'.` `The x86 pipeline is stalled if hazards occur in effective (virtual) addresses. That wouldn't work if two separate processes access the same PA using different VAs.`

post a followup message
(Be nice... or be blocked. Be technical... or be erased.)

`Name:`		`optional link title:`
`eMail:`		`optional link URL:`
`Subject:`		`optional image URL:`
	Insert line breaks by hand when only about one inch remains at the right side. Otherwise your message will be unreadable.
`Text:`	\|\| Both processors share the same pipeline. If the pipeline would care \|\| about read-modify-write conflicts regardless of the executing \|\| thread (as it does for a single thread), then it would be safe to omit \|\| the 'lock'. \| \| \| The x86 pipeline is stalled if hazards occur in \| effective (virtual) addresses. That wouldn't work if two \| separate processes access the same PA using different VAs. \|


	Note: The above eMail form fields may look unaligned if you are using a browser other than Netscape Navigator version 3.0.

currently posted followup messages
(You may have to press the RELOAD button of your browser.)