OPset for vLLM-HUST
OPset is an updateable vLLM-HUST Extension Bundle for independently gated
Ascend operator optimizations and Graph fusions. Version 0.3.0 contains:
persistent-matmul-empty: replaces the redundanttorch.zerosallocation in Ascend batch-invariant Tritonlinear_persistentwithtorch.empty.linear-swiglu-graph: fuses adjacent unquantized gate/up GEMM and SwiGLU in the Graph path. The validated decode/small-batch range (M <= 128) uses the fused Triton kernel; larger dynamic prefill shapes fail closed to the native GEMM plusnpu_swiglupath.
Both optimizations are limited to the batch-invariant Graph/Triton path and do not change ordinary ACLNN MatMul or unrelated linear implementations. Existing NPU evidence covers supported dtypes, divisible and non-divisible shapes, and matched operator/end-to-end measurements. Unknown source structures are rejected rather than patched.
Architecture
The distribution exposes two entry points:
vllm_hust.extension_bundlesletsvllm-hust-extdiscover, check and enable the0.2-experimentalbundle.vllm.general_pluginsinstalls a lazy import hook in each vLLM process. The hook changes only enabled target modules and has no device or network side effects at import time.
Optimizations are selected with VLLM_HUST_OPERATOR_OPTIMIZATIONS. The bundle
manager enables both shipped optimizations; either ID can also be selected
independently.
Install and use
This distribution succeeds vllm-hust-operator-optimizations. Existing
Python imports, extension IDs, environment variables, and the
vllm-hust-operator-check command remain available. Upgrade an existing
installation with:
pip uninstall -y vllm-hust-operator-optimizations
pip install vllm-hust-opset==0.3.0
The package records the fixed experiment line in
compatibility/verified-line.json. This keeps current results reproducible
without repeatedly rebuilding the environment; the line will be refreshed and
revalidated periodically as the underlying stack advances.
export VLLM_SRC=/path/to/vllm
export VLLM_ASCEND_SRC=/path/to/vllm-ascend-hust
pip install vllm-hust-opset==0.3.0
vllm-hust-opset \
--vllm-src "$VLLM_SRC" \
--vllm-ascend-src "$VLLM_ASCEND_SRC"
vllm-hust-ext extension check org.vllm-hust.operator-optimizations
vllm-hust-ext extension enable org.vllm-hust.operator-optimizations
VLLM_BATCH_INVARIANT=1 vllm-hust-ext run -- vllm serve /path/to/model \
--block-size 128
TRITON_ASCEND_SRC may additionally point to the locked Triton checkout. If
it is absent, the checker verifies the installed triton-ascend==3.2.2
wheel; this is the mode used by the validated server environment.
Repository maintainers can build with uv build --no-sources --out-dir dist
and use scripts/install_verified_line.sh to gate and install a local wheel.
If VLLM_PLUGINS is manually set, it must include both the Ascend platform
plugin name and operator_optimizations; otherwise vLLM intentionally filters
out this runtime entry point.
Add another optimization
- Add an
Optimizationimplementation underoptimizations/with a stable ID, target module and fail-closedapply()method. - Register it in
registry.register_builtins(). - Add its ID to the manifest environment value if it should be enabled by this bundle version, or publish a separately selectable bundle profile.
- Add unit correctness tests and NPU shape/tail, operator-share and matched end-to-end evidence.
- Increment
_version.pyand the manifestextension_versiontogether.
The framework deliberately keeps every optimization independent so a future release can add, disable or reject one optimization without changing the others.
Validation
uv run --with pytest pytest
uv run --with ruff ruff check src tests
uv build --no-sources --out-dir dist
For 0.3.0, the linear-SwiGLU Graph path was validated with Qwen2.5-7B,
ShareGPT, three matched baseline/candidate rounds and operator correctness
coverage. Steady-state TPOT decreased by 3.82% and output-token throughput
increased by 5.24%. Release checks remain extension list, inspect, check,
and run --dry-run; full NPU validation is refreshed periodically or when the
optimization changes.
Metadata
Release files for vllm-hust-opset 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| vllm_hust_opset-0.3.0.tar.gz | 15.9 kB | Without provenance | Details for vllm_hust_opset-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| vllm_hust_opset-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for vllm_hust_opset-0.3.0-py3-none-any.whl |
Total release size: 33.5 kB
Release files / vllm_hust_opset-0.3.0.tar.gz
| Download URL | vllm_hust_opset-0.3.0.tar.gz |
|---|---|
| Size | 15.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
69e2d49e7965a2eda0ea5fe0b4506d0512b72beac90e7f06986837f0702ea226
|
|
BLAKE2b-256 checksum How to use checksums |
b0c167e20ee8282b396fb62ee8af49cec1e2a38907d4bb06d1f51245e00eeefb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.15 {"installer":{"name":"uv","version":"0.11.15","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / vllm_hust_opset-0.3.0-py3-none-any.whl
| Download URL | vllm_hust_opset-0.3.0-py3-none-any.whl |
|---|---|
| Size | 17.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8c4e24100fce38391f4b4cce11c323d6950128d1dc1fcfb4e374a842157efe52
|
|
BLAKE2b-256 checksum How to use checksums |
cb2f9e1726f34da7a31f217b04e7fb1689e7bf0f65eea988f7810dfbba81f159
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.15 {"installer":{"name":"uv","version":"0.11.15","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for vllm-hust-opset 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.