Re: [Gems-users] Having more than one cache request go out simultaniously per processor

["Dan Gibson" <degibson@xxxxxxxx>]

This is not currently possible when executing only with Ruby, as Simics models 'in-order' cores. When running with Opal, you should occasionally observe multiple accesses per cycle from the same core.

Regards,
Dan

On Thu, Oct 23, 2008 at 3:48 PM, Fuad Tabba <fuad@xxxxxxxxxxxxxxxxx> wrote:

Hi,

In the process of diving into GEMS and understanding it thoroughly, I was wondering if it is possible to issue more than one cache request at a time, by the same processor, for different locations. If I understand the GEMS code, it seems that there can be up to g_SEQUENCER_OUTSTANDING_REQUESTS outstanding issued requests per processor? Is that right?

In practice, from looking at the code, I've only seen that happen in writing a log, where a store GetX request would be issued for both the location and the log entry itself.

This could be useful for prefeching items that might be needed soon...

Any ideas? Caveats that I should be aware of?

Thanks.

Cheers,
/fuad

_______________________________________________
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!