Skip to content
This repository was archived by the owner on May 11, 2025. It is now read-only.

Why not set stream in gemmv2_forward_cuda and dequantize_weights_cuda #23

@grimoire

Description

@grimoire

Hi, thanks for the great work.

I am working on deploy model on distributed environment. Since dequantize_weights uses the default stream, Kernels would be overlap with NCCL all_reduce kernel, which leads to unexpected result.

dequantize_weights<<<num_blocks, threads_per_block>>>(kernel, scaling_factors, zeros, de_kernel, G, in_c, out_c);

W1WQQyhNsv

Is there any reason to use the default stream here?

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