Re: [Gems-users] Request stalling in ordered MessageBuffer

[Dan Gibson <degibson@xxxxxxxx>]

Requests for separate lines will not block eachother. GETS Y will be 
served, even in an earlier GETS X is waiting on a busy state. The 
ordered queues are ordered with respect to block address.
Regards,
Dan

Hemayet Hossain wrote:
> Reposting ...
>
> Hi,
> I have some confusion over stalling in ordered queue(MessageBuffer). I 
> am using GEMS1.3. Can someone please clear the issue?
> Straight: Can a blocked (due to busy line) request stall another request following in the ordered request queue but the line is ready to serve that request? 
>
> Assume, I have a GETS request for a cache line X, which is in busy state 
> now, at shared L2; so GETS is stalled. Another GETS request for cache line 
> Y, which is in stable state, comes. Will the GETS for Y be stalled too 
> as it is behind GETS for X and ordered queue? Or, GETS of Y will be 
> served? I am using MSI_MOESI_CMP_directory protocol.
> Thanks,
> Hemayet
>
>
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
> Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.
>
>   
--
http://www.cs.wisc.edu/~gibson [esc]:wq!