Re: [Gems-users] COMMIT_XACT cache request in LogTM

[Luke Yen <lyen@xxxxxxxxxxx>]

  It is left over code from when I integrated TM support into Opal (for 
the LogTM-SE project).
  Luke


On Fri, 3 Oct 2008, Lois Orosa Nogueira wrote:

> Hi list,
>
> I'm looking the sequencer.C, and I see in the function getNumberOutstandingDemand() the code:
>
> ...
>     Vector<Address> keys = m_readRequestTable_ptr[p]->keys();
>     for (int i=0; i< keys.size(); i++) {
>       CacheMsg& request = m_readRequestTable_ptr[p]->lookup(keys[i]);
>       // don't count transactional begin/commit requests
>       if(request.getType() != CacheRequestType_BEGIN_XACT && request.getType() != CacheRequestType_COMMIT_XACT){
>         if(request.getPrefetch() == PrefetchBit_No){
>           total_demand++;
>         }
>       }
>     }
> ...
>
> I thought that commit and begin magic instructions didn't arrive at sequencer (I thought that it arrived directly to TransactionInterfaceManager).
> Can somebody explain me this??
>
> Thanks
> Lois