> > It supposed to profile misses. It may not be hooked
> > up right.
> >
>
> Maybe it is something very simple but we still don't
> understand what means to profile misses. What is this
> action doing?
>
It counts L2 misses in $GEMS/ruby/profiler/Profiler.C
>
> > > Why does the L2 consider local and non local L1
> > > caches and has different states for them?
> > >
> >
> > I'm not sure what you mean. You can refer to a
> > particular place?
> >
>
> We refer to the different events defined in the L2
> such as L1_GETX and Fwd_GETX. We see that they can
> come from an L1 or an L2. It's suposed that only local
> L1 ask the L2 (L1_GETX) and other L1s need to go
> through their L2 (Fwd_GETX) to get the block?
> Because for Fwd_GETX it says "GetX from another
> processor", does this mean another chip?
>
Yes, this is exactly what that means. A Fwd_GETX comes from the L2
controller from another chip.
Sorry for the bad comments.
--Mike
|