Skip to content

Revised Unified Virtual Memory(UVM) support #107

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

Open
wants to merge 154 commits into
base: dev
Choose a base branch
from

Conversation

yechen3
Copy link

@yechen3 yechen3 commented Mar 7, 2025

Same to PR#85, but this has a cleaner commit history.

DebashisGanguly and others added 30 commits February 13, 2018 20:54
- Full functional implementation; Performance/time simulation pending
- CUDA APIs for cudaMallocManaged, cudaMemPrefetchAsync, and cudaDeviceSynchronize
- Data-structures to maintain mapping between CPU and GPU side memory during cudaMallocManaged
- Track mapping during cudaSetupArgument to override CPU memory pointer by GPU side memory pointer
- Same benchmark with cudaMalloc and cudaMemcpy, i.e., old APIs
- Same benchmark with cudaMallocManaged, i.e., new UVM API
- Adding PCI-e latency as part of config (value subject to change based on architecture)
- Parsing logic of latency and setting clock domain
- Adding valid flag as part of page table implementation
- TLB look up
- page table access/walk latency
- multi-lane bidirectional PCI-E with far fetch latency
- Don't process if warp instruction's access queue is empty
- Change input size for bfs, nw, pathfinder, srad_v2 etc. to finish in reasonable time
- Add pathfinder benchmark for managed code
- Fixing BFS managed code
…ze, and a bollean flag to denote whether data is copied from cpu to gpu on first kernel launch
… queue is ready to complete.

Determine based on whether dispatched warps from all SMs are stalling for PCI-E transfer and no progress can be made by any component of the simulator.
…ion write back or device synchronize check for allocations which were copied at the first place during kernel launch from CPU to GPU
@yechen3 yechen3 requested a review from tgrogers March 7, 2025 11:03
Copy link

@tgrogers tgrogers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yechen3 - one weird side-effect of the integration changes is that you ended up re-adding a bunch of files that have since been deleted. Jenkinsfile, bitbucket*, all the old configs in the old folders outside of tested and deprecated.

Please clean this up. Make sure you are only adding files that are actually added for this to work. Otherwise, the directory structure should be the same as the mainline dev.

@yechen3
Copy link
Author

yechen3 commented Mar 17, 2025

@tgrogers Got it. I've already cleaned things up, so everything should be in order now. Let me know if there's anything else that needs attention.

@yechen3 yechen3 requested a review from tgrogers April 23, 2025 20:25
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 this pull request may close these issues.

4 participants