discussion forum message Name: Peter M. Date: June 11, 2003 at 05:07:55 Subject: Re: Hyperthreading and 'lock' prefix In Reply To: Hyperthreading and 'lock' prefix by Stephan Keil on June 10, 2003 at 02:30:56 Text: Now since the LOCK# mechanism also keeps other bus mastering agents away from the resource you're trying to access, the general rule is to use it whenever you need to do an atomic access - no matter how many CPUs there are. 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: | Now since the LOCK# mechanism also keeps other bus mastering agents away from the resource you're trying to access, the general rule is to use it whenever you need to do an atomic access - no matter how many CPUs there are. |     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.) Re: Hyperthreading and 'lock' prefix by Stephan Keil, 06:07:58 2003/06/16 (2) Re: Hyperthreading and 'lock' prefix by james, 12:29:35 2003/06/16 (1) Re: Hyperthreading and 'lock' prefix by Stephan, 02:38:54 2003/06/17 (0)