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

feat: Remove more unnecessary PTX code from Wave #12380

Closed
wants to merge 3 commits into from

Conversation

dreveman
Copy link
Collaborator

No description provided.

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Feb 18, 2025
@dreveman dreveman requested review from Yuhta and removed request for majetideepak and assignUser February 18, 2025 21:38
Copy link

netlify bot commented Feb 18, 2025

Deploy Preview for meta-velox canceled.

Name Link
🔨 Latest commit 639d121
🔍 Latest deploy log https://app.netlify.com/sites/meta-velox/deploys/67c081565b4d980008ce696c

@dreveman dreveman changed the title feat: remove more unnecessary PTX code from Wave feat: Remove more unnecessary PTX code from Wave Feb 18, 2025
@Yuhta Yuhta added the ready-to-merge PR that have been reviewed and are ready for merging. PRs with this tag notify the Velox Meta oncall label Feb 19, 2025
@dreveman dreveman force-pushed the rm-ptx-2 branch 2 times, most recently from 69ee8b3 to 540a750 Compare February 19, 2025 17:31
@dreveman
Copy link
Collaborator Author

@Yuhta any reason for why this is taking so long to be merged?

@facebook-github-bot
Copy link
Contributor

@mbasmanova has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@mbasmanova
Copy link
Contributor

@dreveman Seeing format error:
Screenshot 2025-02-27 at 12 53 18 AM

@kgpai @majetideepak @assignUser Wondering why this doesn't show up in CI.

@majetideepak
Copy link
Collaborator

@mbasmanova Likely a clang-format version difference. Can you share the version being used internally?

@mbasmanova
Copy link
Contributor

@majetideepak clang-format version 18.1.3

@assignUser
Copy link
Collaborator

clang-format version 18.1.3

That's what's in our container as well. I think the reason is that we only run the check on touched files and the file in question wasn't touched by this PR. Maybe the internal linter works on a dir basis and not a file basis or something?

@mbasmanova
Copy link
Contributor

@assignUser velox/experimental/wave/common/Cuda.cu is modified in this PR. Do we run format-check on .cu files?

@assignUser
Copy link
Collaborator

assignUser commented Feb 27, 2025

Yes now it is but only to fix the lint. Or did I have a weird diff view?

@assignUser
Copy link
Collaborator

Oh sorry I read the linter wrong, without space is correct. Hm, let me check.

David Reveman added 3 commits February 27, 2025 10:10
Shouldn't impact performance. If anything, might be faster as
threadIdx.x is likely in a register already and %laneid requires
a S2R instruction that can have a relatively long latency
compared to a regular register.
Add build option that disables Wave branch kernel test as
it requires PTX. This test is enabled by default and can be
disabled with:

cmake -DVELOX_SKIP_WAVE_BRANCH_KERNEL_TEST=ON
@dreveman
Copy link
Collaborator Author

Sorry, not sure how that format change become part of that commit. Must have run the formatting script locally with the wrong clang-format version. Rebased and removed that format change from latest version of PR.

@assignUser
Copy link
Collaborator

assignUser commented Feb 27, 2025

When I add the space locally and run make format-fix in the check container the cli reports that it checked the file Fix : velox/experimental/wave/common/Cuda.cu but the file isn't actually changed.

But two spaces are corrected to a single one. So this must be an issue with our clang-format file.

@facebook-github-bot
Copy link
Contributor

@mbasmanova has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@assignUser
Copy link
Collaborator

assignUser commented Feb 27, 2025

I looked at the docs and tested something but was unable to pin down the issue. My local lsp (using the same clang format version) enforces one space after the ctor initializer list and uses the same .clang-format file as make format-fix 🤷

@mbasmanova maybe you can diff you internal clang-format file with the public one in the repo to find the misaligned setting. But the manual fix works for now too I guess ^^

@mbasmanova
Copy link
Contributor

@kgpai

maybe you can diff you internal clang-format with the public one in the repo to find the misaligned setting.

Krishna, is this something you could help with?

@facebook-github-bot
Copy link
Contributor

@mbasmanova merged this pull request in 0d8c05a.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Merged ready-to-merge PR that have been reviewed and are ready for merging. PRs with this tag notify the Velox Meta oncall
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants