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

Add Dockerfile.hpu #200

Merged
merged 2 commits into from
Sep 13, 2024
Merged

Conversation

xuechendi
Copy link

Add Dockerfile.hpu

FIX #199

BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE


PR Checklist (Click to Expand)

Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.

PR Title and Classification

Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

  • [Bugfix] for bug fixes.
  • [CI/Build] for build or continuous integration improvements.
  • [Doc] for documentation fixes and improvements.
  • [Model] for adding a new model or improving an existing model. Model name should appear in the title.
  • [Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
  • [Kernel] for changes affecting CUDA kernels or other compute kernels.
  • [Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
  • [Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
  • [Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.

Code Quality

The PR need to meet the following code quality standards:

  • We adhere to Google Python style guide and Google C++ style guide.
  • Pass all linter checks. Please use format.sh to format your code.
  • The code need to be well-documented to ensure future contributors can easily understand the code.
  • Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
  • Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes

Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.

What to Expect for the Reviews

The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

  • After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
  • After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
  • After the review, the reviewer will put an action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
  • Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You

Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

Signed-off-by: Chendi.Xue <chendi.xue@intel.com>
@xuechendi
Copy link
Author

git clone https://github.com/vllm-fork/vllm.git
docker build -f Dockerfile.hpu -t vllm-hpu-env --shm-size=4g .
docker run -it --rm --runtime=habana --name=vllm-hpu  --network=host -v ./models:/workspace/models -e HF_HOME=/workspace/models -e HF_TOKEN=${HF_TOKEN} vllm-hpu-env --model meta-llama/Meta-Llama-3.1-8B-Instruct

@Xaenalt
Copy link

Xaenalt commented Aug 29, 2024

Oh cool, might need to incorporate some of those changes in #190 what does PT_HPU_ENABLE_LAZY_COLLECTIVES do?

@kzawora-intel kzawora-intel added the intel Issues or PRs submitted by Intel label Aug 29, 2024
@kzawora-intel
Copy link

Oh cool, might need to incorporate some of those changes in #190 what does PT_HPU_ENABLE_LAZY_COLLECTIVES do?

PT_HPU_ENABLE_LAZY_COLLECTIVES enables usage of collective operations (mostly allgather and allreduce in vLLM's case) in HPUGraphs. It is not needed for single-card inference, but required for using tensor parallelism with HPUGraphs.

Dockerfile.hpu Outdated Show resolved Hide resolved
Signed-off-by: Chendi.Xue <chendi.xue@intel.com>
Copy link

@michalkuligowski michalkuligowski left a comment

Choose a reason for hiding this comment

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

lgtm

@michalkuligowski michalkuligowski merged commit f4ac1f9 into HabanaAI:habana_main Sep 13, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
intel Issues or PRs submitted by Intel
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feature]: Add Dockerfile.HPU
4 participants