On Wed, 24 Oct 2012, Cookie wrote:
Hi Nilay,
Thank you for your reply. In MESI_CMP_directory-L1cache.sm, there are
several latency parameters: l1_request_latency, l1_response_latency, and
to_l2_latency. Do you mean these parameters decide the communication time?
However, I didn't see any different latencies between a local access (L1D-0
to L2-0) and a remote access (L1D-0 to L2-1). For example, in
action(b_issueGETX), the out_msg.Destination varies based on the return
value of mapAddressToRange(), however, the latency is statically set as
l1_request_latency, which is 2 in default. Also there are other two actions
which involve delayed cycles (which call profileMsgDelay()), but I've no
idea if it is related to the varied communication time.
There is no such thing as local or remote access from this protocol's
point of view.
I expect to control the communication time myself. For example, if it is a
local access from a L1 cache to its own L2 cache slice (L1D-0 to L2-0), the
access latency is 2; if it is a remote access from a L1 cache to a remote
L2 cache slice (L1D-0 to L2-3), the access latency is 2 * num_of_hops (2*4
in this case). So I thought it should be calculated based on the distance
from the requestor to the destination. But I cannot find anywhere that is
related to it. So could you please give me any hints on how to deal with
it? Do I misunderstand it at all? Thank you for your help.
You can set up the interconnection network to mimic the design that you
care for.
--
Nilay
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
