The patch was incorporated into some other recent ruby stat changes
recently (1-2 weeks): specifically the removal of the cache profiler, and
the counting of hits/misses directly in the sm file. So you should probably
update.

The other thing is, I think your complicating your calculations a bit:

L2 miss rate = 100*(total L2 misses for all L2 banks) / (total L1 Dcache
misses+total L1 Icache misses)

Specifically, how are you going to access an L1 cache miss count/rate from
an L2 cache in the code? You should just stick to basics when thinking
about rates (%/total%): Whenever a request comes from L1port to L2 cache,
it is an access, and when that access "misses" (the request has to be
forwarded/sent up to directory) it is a miss type.

Malek



On Wed, Jun 12, 2013 at 12:51 PM, Mahshid Sedghi
<mahshid.sed...@gmail.com>wrote:

> Thanks for your reply Maxime. But is there anything wrong with the way I
> calculate the rates? I see that the patch has been submitted for review
> long time back, but has not been applied to the gem5 release yet. Is this
> patch reliable?
>
> Thanks.
> Mahshid
>
>
> On Wed, Jun 12, 2013 at 7:29 AM, Maxime Chéramy 
> <maxime.cher...@gmail.com>wrote:
>
>> Have a look to http://reviews.gem5.org/r/1467/ but the support of
>> MESI_CMP is not correct, you'll have to do some changes.
>>
>> 2013/6/12 Mahshid Sedghi <mahs...@cse.psu.edu>
>>
>>> Hi all,
>>>
>>> I'm trying to calculate L1 and L2  cache miss rates for a full system
>>> simulation using ruby (MESI_CMP_directory) + garnet. I dump stats
>>> periodically to get the trend of the rates. I can see that in ruby.stats,
>>> total_misses for each L1 and L2 cache bank is reported. Also, I can see the
>>> events which are happening inside the coherency protocol. So, I use the
>>> total "Load" and "Store" counts and calculate the miss rates as the
>>> following:
>>>
>>> L1 Dcache miss rate = 100* (total L1D misses for all L1D caches)
>>> /(Loads+Stores)
>>>
>>> L2 miss rate = 100*(total L2 misses for all L2 banks) / (total L1 Dcache
>>> misses+total L1 Icache misses)
>>>
>>> But for some reason, the rates I am getting does not make sense. I was
>>> wondering if this is the right way to calculate the miss rates using ruby
>>> statistics.
>>>
>>> I appreciate any help.
>>>  Mahshid
>>>
>>> _______________________________________________
>>> gem5-users mailing list
>>> gem5-users@gem5.org
>>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>>>
>>
>>
>> _______________________________________________
>> gem5-users mailing list
>> gem5-users@gem5.org
>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>>
>
>
> _______________________________________________
> gem5-users mailing list
> gem5-users@gem5.org
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to