Re: [Gems-users] how does L1 cache with block state "S" handle Fwd_GetS from L2 cache

[Niket Agarwal <niketa@xxxxxxxxxxxxx>]

Yes, there is no way to connect different MessageBuffers to different  
links, even now, in the default GEMS.
I think the point being made is that the same virtual network can be  
used for different kind of messages. In this case the L1->L1 and L2->  
L1 responses use the same virtual network. Virtual networks are only  
used avoid protocol-level deadlocks and otherwise have no restriction  
on what messages go in which virtual network.
Niket

On Oct 11, 2009, at 9:20 AM, Mike Marty wrote:

> 2009/10/11 shanshuchang <shanshuchang@xxxxxxxxx>:
> > Thanks for the reply.
> > You mean that different L1s can communicate with each other  
> > directly through
> > MessageBuffers as long as they have the same virtual network number?
> There must be connectivity in the network configuration as well.
> There would only be a lack of connectivity if you used FILE_SPECIFIED
> network and forgot to connect an L1 controller (or had a partition in
> the topology).
>
> The MessageBuffers all connect to the same network link.  As far as
> I'm currently aware (and I haven't used GEMS in nearly 2 years), there
> is no way to associate different MessageBuffers with different links
>
> --Mike
> _______________________________________________
> 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.