vllm.model_executor.layers.fused_moe.runner.moe_runner ¶
MoERunner ¶
Bases: MoERunnerInterface
Standard MoE runner implementation for executing Mixture of Experts layers.
This is the primary concrete implementation of MoE execution logic, providing comprehensive support for standard MoE operations. It handles: - Expert routing and token dispatching using various routing strategies - Shared experts computation with optional parallel execution using CUDA streams - Tensor model parallel and expert parallel operations - Multiple quantization methods and optimized kernel selection - Both monolithic and decomposed expert execution paths - Integration with various parallel execution modes (TP, EP, DP)
The runner orchestrates the complete MoE forward pass including routing tokens to experts, executing expert computations in parallel, and combining results. It supports advanced features like overlapped execution of shared experts, optimized kernels for different parallel configurations, and seamless integration with vLLM's distributed execution framework.
Eventually, this class may be split into more specialized implementations for different configurations (e.g., with/without shared experts, gates, etc.).
Source code in vllm/model_executor/layers/fused_moe/runner/moe_runner.py
174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 | |
_apply_quant_method ¶
_apply_quant_method(
layer: Module,
hidden_states: Tensor,
router_logits: Tensor,
shared_experts_input: Tensor | None,
) -> tuple[Tensor | None, Tensor]
Run expert routing and the fused MoE kernel via the quant method.
Orchestrates shared expert execution (before/after), expert selection via the router, and the actual fused MoE computation. Returns (shared_expert_output, fused_expert_output).
Source code in vllm/model_executor/layers/fused_moe/runner/moe_runner.py
_forward_impl ¶
_forward_impl(
layer: Module,
hidden_states: Tensor,
router_logits: Tensor,
shared_experts_input: Tensor | None,
) -> Tensor | tuple[Tensor, Tensor]
Entry point called by the custom op to run the MoE computation.
Handles pre-dispatch setup (gate application, external shared expert triggering, quant config init) then performs the following steps within the sequence-parallel context.
- Performs expert routing
- fused MoE kernel execution
- shared expert computation.
Returns a single tensor of combined fused and shared output (if present).
Source code in vllm/model_executor/layers/fused_moe/runner/moe_runner.py
_maybe_add_zero_expert_output ¶
Add the zero expert's contribution to the final result.
When a ZeroExpertRouter is used, it computes a bias-like output from the "zero expert" that is added to the combined routed+shared expert output.
Source code in vllm/model_executor/layers/fused_moe/runner/moe_runner.py
_maybe_apply_routed_scale_to_output ¶
_maybe_apply_routed_scale_to_output(
shared_output: Tensor | None, fused_output: Tensor
) -> tuple[Tensor | None, Tensor]
Apply routed_scaling_factor to the output with FP16 overflow protection.
Scale the fused expert output by routed_scaling_factor. For FP16, avoid overflow by dividing shared_output by the scale instead (the decoder layer compensates with matching divisions).
Source code in vllm/model_executor/layers/fused_moe/runner/moe_runner.py
_maybe_pad_hidden_states ¶
_maybe_pad_hidden_states(
shared_experts_input: Tensor | None,
hidden_states: Tensor,
) -> tuple[Tensor, int]
Pad hidden_states to moe_config.hidden_dim and compute the original dimension for later truncation.
For latent MoE, the routed hidden_states may be smaller than hidden_dim. Padding ensures uniform tensor sizes through the fused MoE kernel. The returned trunc_size is used by _maybe_reduce_final_output to strip the padding from the result.
Source code in vllm/model_executor/layers/fused_moe/runner/moe_runner.py
_maybe_reduce_final_output ¶
Truncate padded dimensions and all-reduce the combined output.
This is the "late" all-reduce path. When neither fused nor shared output was individually reduced, the combined sum is all-reduced here. Skipped when sequence-parallel is active (SP handles its own reduction) or when the early path already reduced both outputs.
Source code in vllm/model_executor/layers/fused_moe/runner/moe_runner.py
_maybe_reduce_shared_expert_output ¶
All-reduce shared expert output when the combine kernel already reduced fused output.
- If the combine kernel does the reduction for fused_output, reduce shared_output separately. O.w, reduce fused_output+shared_output later.
- If we have SP (TP=N, DP=M, EP), there is a separate AG step handled in the model.
Source code in vllm/model_executor/layers/fused_moe/runner/moe_runner.py
_sequence_parallel_context ¶
Return a context manager for sequence-parallel token redistribution.
When sequence parallelism is active, returns a context that handles local size tracking for proper token scatter/gather. Otherwise returns a no-op context.
Source code in vllm/model_executor/layers/fused_moe/runner/moe_runner.py
apply_routed_input_transform ¶
Apply transform for routed experts (e.g., latent projection).
This is called by FusedMoE.forward_native. The original hidden_states is saved separately so shared experts get [S, hidden_size] while routed experts get the transformed [S, moe_latent_size].
Returns (possibly transformed) hidden states and the input for shared experts (or None if there are no shared experts).
Source code in vllm/model_executor/layers/fused_moe/runner/moe_runner.py
apply_routed_output_transform ¶
Apply transform to routed expert output (e.g., latent to full dim).
Used by latent MoE models (e.g., NemotronH) where routed experts operate in a compressed latent space and need projection back to the full hidden dimension before combining with shared expert output.
Source code in vllm/model_executor/layers/fused_moe/runner/moe_runner.py
forward ¶
Invoke the fused moe layer.
Input: - hidden_states - router_logits
Output: - The new hidden_states.
Calling sequence - forward - self._forward_entry (_moe_forward or _moe_forward_shared custom op) - _forward_impl
Note: The existence of _moe_forward and _moe_forward_shared custom ops are due to the following reason: 1. pytorch cannot handle union types in custom op signatures so _moe_forward and _moe_forward_shared must be split.
Source code in vllm/model_executor/layers/fused_moe/runner/moe_runner.py
522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 | |