Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

-h gives conflicting information regarding default data cache kind #17

Closed
Emoun opened this issue Feb 17, 2021 · 2 comments · Fixed by #27
Closed

-h gives conflicting information regarding default data cache kind #17

Emoun opened this issue Feb 17, 2021 · 2 comments · Fixed by #27

Comments

@Emoun
Copy link
Member

Emoun commented Feb 17, 2021

When running pasim -h the following is printed regarding the data cache kind:

-D [ --dckind ] arg (=dm)             kind of direct mapped/fully-/set-associ
                                        ative data cache, defaults to lru2
                                        (ideal, no, dm, lru[N], fifo[N])

The (=dm) should signify that a direct mapping is used when the flag is not set, however the description then says defaults to lru2.

Running some tests, it seems to me that direct mapping is indeed the default when the flag is not set.
We should decide which kind should be default and correct the message to fit.

@Emoun
Copy link
Member Author

Emoun commented Feb 10, 2022

@schoeberl do you have input on this? What does the default configuration of patmos use?

@schoeberl
Copy link
Member

The default configuration on Patmos (hardware) is a direct-mapped data cache with write-through.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants