On Mon, July 11, 2011 10:27 pm, lyh wrote:
> Hi All,
> While implementing the cache coherence protocol for a cc-NUMA system,the
> directory structure(e.g.directory entry) can be oganizated in many ways,
> for example, full_map bit vector, limited pointers, or multilevel
> directory the first level of which is a directory cache.
> Theoretically, different directory structures have different impacts on
> system performance. How does GEM5 implement directory structures?
> e.g.
> In file MESI_CMP_directory-dir.sm, the DirectoryEntry is a so-called
> AbstractEntry, how can this implementation simulate the true situation?
> // DirectoryEntry
> structure(Entry, desc="...", interface="AbstractEntry") {
> State DirectoryState, desc="Directory state";
> DataBlock DataBlk, desc="data for the block";
> NetDest Sharers, desc="Sharers for this block";
> NetDest Owner, desc="Owner of this block";
> }
>
As per my understanding of the MESI CMP directory protocol, a full bit
vector is maintained.
--
Nilay
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
