vllm.model_executor.layers.fused_moe.router.gate_linear
¶
Classes:
-
GateLinear–MoE gate linear layer with multi-tier GEMM dispatch:
Functions:
-
fp32_router_gemm_dispatch_impl–Dynamically run fp32 specialized gemm if num_tokens <= FP32_MAX_TOKENS,
-
rocm_bf16x3_router_gemm_dispatch_impl–Run the ROCm bf16x3 router GEMM, or fall back for small batches.
GateLinear
¶
Bases: ReplicatedLinear
MoE gate linear layer with multi-tier GEMM dispatch:
- cuteDSL ll_bf16_gemm (SM90+, M<=16, bf16 in, fp32 out, K divisible by 8)
- fp32 specialized kernel (SM90+ or gfx950, bf16/fp32 in, fp32 out, M<=32, model-specific shapes)
- bf16x3 CuteDSL kernel (SM100, bf16 in, fp32 weight)
- ROCm bf16x3 router GEMM (gfx950, bf16 in, fp32 weight, fp32 out, M>=2048)
- cuBLAS bf16×bf16→fp32 (SM90+ + bf16 weight + fp32 out_dtype)
- F.linear via ReplicatedLinear (ultimate fallback)
The out_dtype attribute is mutable and can be set after init
(e.g. when the required dtype depends on the expert quantization
method which is only known later).
A quant_config that actually quantizes the gate disables every
specialized tier, leaving plain ReplicatedLinear behavior.
Methods:
-
set_out_dtype–Set output dtype for the router logits after init.
Source code in vllm/model_executor/layers/fused_moe/router/gate_linear.py
20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 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 | |
set_out_dtype(out_dtype)
¶
Set output dtype for the router logits after init.
Useful when the required dtype depends on the expert quantization method which is only known after the gate is constructed.
Source code in vllm/model_executor/layers/fused_moe/router/gate_linear.py
_GateLinearMethod
¶
Bases: UnquantizedLinearMethod
UnquantizedLinearMethod plus the ROCm bf16x3 weight split.
Building the split here rather than lazily in forward() charges it to the
weights memory pool ahead of KV cache profiling, and rebuilds it on weight
reload. The latter matters because an in-place param.data.copy_()
leaves both data_ptr() and _version untouched, so a stale split
cannot be detected from inside forward().
allow_rocm_bf16x3_router_gemm is final by the time this runs: the only
caller of set_out_dtype does so during model construction.
Source code in vllm/model_executor/layers/fused_moe/router/gate_linear.py
fp32_router_gemm_dispatch_impl(x, weight, allow_bf16x3_router_gemm)
¶
Dynamically run fp32 specialized gemm if num_tokens <= FP32_MAX_TOKENS, otherwise optionally run the experimental BF16x3 kernel for medium/large SM100 router batches, then fall back to F.linear. This must be wrapped in a custom op because our torch.compile integration does not support runtime dispatching on num_tokens.
Source code in vllm/model_executor/layers/fused_moe/router/gate_linear.py
rocm_bf16x3_router_gemm_dispatch_impl(x, weight, weight_split)
¶
Run the ROCm bf16x3 router GEMM, or fall back for small batches.
This must be a custom op because our torch.compile integration does not
support runtime dispatching on num_tokens: models carrying fp32 router
weights (MiniMax-M2, HunYuan-V3) call the gate from
@support_torch_compile model code and vLLM drops all Dynamo guards, so
a plain Python branch on x.shape[0] would be frozen at first trace.