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

[Core] Changes to support 0.2.0 flashinfer #11314

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

pavanimajety
Copy link
Contributor

@pavanimajety pavanimajety commented Dec 19, 2024

Dataype and wrapper changes for 0.2.0 flashinfer

Related: #11194

Copy link

👋 Hi! Thank you for contributing to the vLLM project.
Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can do one of these:

  • Add ready label to the PR
  • Enable auto-merge.

🚀

@pavanimajety pavanimajety marked this pull request as draft December 19, 2024 01:00
@pavanimajety pavanimajety force-pushed the flashinfer-0.2-changes branch from c1e4b21 to 5439e7d Compare December 19, 2024 02:29
@pavanimajety pavanimajety marked this pull request as ready for review December 19, 2024 02:37
@JaheimLee
Copy link

I found flashinfer 0.2.0 uses more memory on rank 0 when tp>1. I built it from source with AOT mode. Is that normal?

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.

2 participants