Re: NdisInterLockedIncrement/Decrement macros

soviet_bloke@xxxxxxxxxxx wrote:
You are allowed to use LOCK prefix only with the instructions that I
mentioned above, and MOV is not among them.

It is not allowed because it is useless on x86, anyway.

Also, reading a variable will always be atomic on all CPUs, even on
RISC or whatever (assumed the variable is correctly aligned).

Thus, there is abosuletly no need for any locking here.

Stephan

.

Relevant Pages

  • Re: Build and Sysgen
    ... have to worry about a reinstall. ... > Working on CE 5 OS for and X86 VIA based product. ... Have been reading the ... > Paul A. Lowe ...
    (microsoft.public.windowsce.platbuilder)
  • Build and Sysgen
    ... Working on CE 5 OS for and X86 VIA based product. ... Have been reading the ... newsgroups and noticed postings on Build and Sysgen option. ... Paul A. Lowe ...
    (microsoft.public.windowsce.platbuilder)
  • Re: performance
    ... > For example, on x86, the comparison might be like this: ... > mov ax, x ... MASM32 package contains a lot of help files where the timings of ... timings are specified only up to x386. ...
    (comp.lang.cpp)
  • is this task good for Prolog ?
    ... useless. ... operator 3 because D is changed in the very begining and last time A used ... for reading is at 3rd operator. ... How do you think is Prolog a right tool for it? ...
    (comp.lang.prolog)
  • Re: AMD vs Intel performance
    ... >>> skill some day. ... >> Is that why you claimed that OS X would never run on x86? ... LOL... ... > But, then, since you're incapable of reading, that probably doesn't help. ...
    (comp.sys.mac.advocacy)
Quantcast