Re: [Gems-users] Cache Insertion

[Patrick Teague <pjtjr@xxxxxxxxx>]

Thank you.  I will starting looking through that code.  Insertion 
changes on the horizon.
-P

Mike Marty wrote:
> Each coherence protocol, specified by the .sm files, controls how 
> blocks are inserted into the cache.  The "SMP" protocols have private 
> L1 and L2 caches controlled by a single -cache.sm <http://cache.sm> 
> cache controller.  These protocols have exclusive L1/L2 caching.  Many 
> of the "CMP" protocols, with separate -L1cache.sm and -L2cache.sm 
> files, use inclusive L1/L2 caching.
> The cache replacement policy is in the Ruby C++ code (CacheMemory.h)
>
> --Mike
>
>
> On Thu, Sep 11, 2008 at 8:28 PM, Patrick Teague <pjtjr@xxxxxxxxx 
> <mailto:pjtjr@xxxxxxxxx>> wrote:
>     I have been looking through the code for Ruby to try and find where in
>     the code new blocks are inserted.  I have had little success so
>     far.  Is
>     this something that is done by Simics or does Ruby control its own
>     insertion?  Maybe I'm completely off base here?
>
>     -Patrick
>     _______________________________________________
>     Gems-users mailing list
>     Gems-users@xxxxxxxxxxx <mailto: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.
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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.
>
>