8000 [Q & A] Intercepting cudaMallocAsync API may also be suitable to this approach? · Issue #4 · grgalex/nvshare · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
[Q & A] Intercepting cudaMallocAsync API may also be suitable to this approach? #4
Open
@wangao1236

Description

@wangao1236

Hello, I have read your thesis and code and I think your idea is great! However, I have a question. Since the introduction of Stream-Ordered Memory Allocator in CUDA 11.2, cudaMallocAsync and cudaFreeAsync APIs have been provided. If an application calls cudaMallocAsync and it is also intercepted and replaced with cudaMallocManaged, what impact does it have on the calculation results?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0