Hi Kevin,
On 29/07/2019 22:22, Kevin Smith wrote:
> Thanks for the explanation, Nikos! Let me ask about two specific
> (similar) examples which hopefully will clear it up for me.
>
> Let's say L1A sends out a read request r1 for some line. No L1s have the
> line. The L2 has the line in Exclusive s
Hi Kevin,
On 29/07/2019 03:35, Kevin Smith wrote:
> Hi all,
>
> I have a question regarding the classic memory model, about how a cache
> knows when to respond to a peer (neighbor) cache. Please bear with me as
> I try to diagnose what happens and let me know where/if I'm wrong :)
>
In general,
makes sense .
Andreas
From: biswabandan panda mailto:biswa@gmail.com>>
Date: Tuesday, 19 August 2014 03:20
To: Andreas Hansson mailto:andreas.hans...@arm.com>>
Cc: gem5 users mailing list mailto:gem5-users@gem5.org>>
Subject: Re: [gem5-users] Classic memory model
Hi,
te: Monday, 18 August 2014 18:53
>> To: Nizamudheen Ahmed , gem5 users mailing list <
>> gem5-users@gem5.org>
>> Subject: Re: [gem5-users] Classic memory model
>>
>> You could add a parameter say Level to identify the cache level. There
>> is a flag nam
dreas
>
> From: biswabandan panda via gem5-users
> Reply-To: biswabandan panda , gem5 users mailing
> list
> Date: Monday, 18 August 2014 18:53
> To: Nizamudheen Ahmed , gem5 users mailing list <
> gem5-users@gem5.org>
> Subject: Re: [gem5-users] Classic memory model
>
gt;,
gem5 users mailing list mailto:gem5-users@gem5.org>>
Subject: Re: [gem5-users] Classic memory model
You could add a parameter say Level to identify the cache level. There is a
flag named IstopLevel already implemented which distinguishes L1 cache from the
MLCs and LLCs. You could add
You could add a parameter say Level to identify the cache level. There is a
flag named IstopLevel already implemented which distinguishes L1 cache from
the MLCs and LLCs. You could add a similar one to differentiate the caches.
The other way to distinguish the L1 cache is to check the assoc in the
