NOP SPU

Hi.

I had a question about the NOP spu.  I noticed that for Extended Opcode calls which return information all happen to call functions within the state_tracker\state_regcombiner.c file.  

I assume this is to maintain some sort of state on the crserver side.  Does the application client sit and wait to receive a return call (crNetSend->crNetRecv) for these Extended Opcode calls, or is it left waiting forever?  

Does anyone have a good explanation as to what the NOP does when it receives these Extended Opcodes?

Thanks,
Alicia

   


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click