Skip to content

Implement Data Cache Unit and introduce it into the pipeline #17

Open
pavelkryukov opened this issue Apr 14, 2016 · 9 comments
Open

Implement Data Cache Unit and introduce it into the pipeline #17

pavelkryukov opened this issue Apr 14, 2016 · 9 comments
Labels
4 Features of medium complexity which usually require infrastructure enhancements. enhancement Adds a new feature to simulation. S2 — Caches To solve the issue, you NEED knowledge about caches. OOO hierarchy etc.

Comments

@pavelkryukov
Copy link
Member

pavelkryukov commented Apr 14, 2016

We have a cache model implemented, but it is not connected to PerfSim.

AMB: Data Cache Unit is implemented and performance studies are made on memory stress trace.

@pavelkryukov pavelkryukov added the enhancement Adds a new feature to simulation. label Apr 14, 2016
@pavelkryukov pavelkryukov changed the title Implement Data Cache Unit and introduce it into the pipeline (4 points) Implement Data Cache Unit and introduce it into the pipeline Apr 18, 2016
@pavelkryukov pavelkryukov added the 4 Features of medium complexity which usually require infrastructure enhancements. label Apr 18, 2016
@pavelkryukov pavelkryukov added the S2 — Caches To solve the issue, you NEED knowledge about caches. OOO hierarchy etc. label Apr 26, 2017
@pavelkryukov pavelkryukov added this to the Performance Model milestone Oct 23, 2017
@pavelkryukov
Copy link
Member Author

On cache hit, pipeline operates as usual
On cache miss, pipeline is stalled. Address of missed line is pushed to a long-latency port which is monitored by separate method (clock_cache). When data is returned, it is filled into cache so pipeline is unstalled.

@pavelkryukov
Copy link
Member Author

@trexxet I assigned you to severing tasks that you may complete during summer. They are 20 points, covering all requirements for 1st and 2nd term.

@pavelkryukov
Copy link
Member Author

@trexxet Do you read my e-mails?

@trexxet
Copy link
Contributor

trexxet commented Jun 15, 2018

@pavelkryukov
I apologize for the delay. I didn't check e-mail due to exams.
I'll take on these tasks right after exams (approximately 22-25 Jun), and I'm sure I'll complete them by the end of summer. However, I need to examine each problem to estimate time to complete them, so I'd like to do it after exams. I hope this wouldn't delay any work on project.

@pavelkryukov
Copy link
Member Author

pavelkryukov commented Jun 25, 2018

@trexxet just a friendly reminder, today is June 25...

@trexxet
Copy link
Contributor

trexxet commented Jun 30, 2018

@pavelkryukov Sorry, I had to retake one of the exams recently.

I think I'll begin with #290 and #354. They are rather simple and would let me understand current project's structure better. They are going to take 1 week if everything is okay, max 2 weeks.
Then I'll switch to syscalls (#122 and #304), I expect that these tasks can be done in 2 weeks.
After that I will do #17 (this), #18 (which I'm not assigned to yet), and #269. They require some study, and I estimate the time to do them in 2-3 weeks.

So, after completing #290 and #354 I'll inform you about my deadlines for other tasks.
Is this okay?

@pavelkryukov
Copy link
Member Author

pavelkryukov commented Jul 1, 2018

Ok.

I think I'll begin with #290

Not sure it is a very simple thing, as it requires some deep dive into GDB internals.

What do you mean by #18? It is completed already IMO.

@trexxet
Copy link
Contributor

trexxet commented Jul 1, 2018

As I see, for #18 some research should be finished to explain logarithmic law.

@pavelkryukov
Copy link
Member Author

Yes, and @alex19999 is responsible for that.

@pavelkryukov pavelkryukov removed this from the Performance Model milestone Oct 10, 2018
@pavelkryukov pavelkryukov pinned this issue Mar 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
4 Features of medium complexity which usually require infrastructure enhancements. enhancement Adds a new feature to simulation. S2 — Caches To solve the issue, you NEED knowledge about caches. OOO hierarchy etc.
Projects
None yet
Development

No branches or pull requests

2 participants