Re: [Gems-users] model for main memory banks and controller

[Bradford Beckmann <beckmann@xxxxxxxxxxx>]

The config parameter g_NUM_MEMORIES sets the number of memory banks.
Each memory (i.e. directory) has a seperate controller instatiation that
responds with the latency "MEMORY_LATENCY".  You can think of it as the
banking of memory is done by the network, above the directory controller.

Brad


On Fri, 4 Mar 2005, Nauman Rafique wrote:

> In the GEMS document submitted to CAN, it was mentioned that Ruby models memory
> controllers and banks of main memory.
> But in SLICC specifications, I found this for most protocols:
> ----------------------------------------------------------------------------
>   action(d_sendData, "d", desc="Send data to requestor") {
>     peek(requestQueue_in, RequestMsg) {
>       enqueue(responseNetwork_out, ResponseMsg, latency="MEMORY_LATENCY") {
> ----------------------------------------------------------------------------
>
> It looks like that would just delay the memory response by MEMORY_LATENCY.
> Is the generated code taking care of banking (or memory controller)?
>
> Thanks
> --
> Nauman
>
>
>
>
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>