vllm.compilation.breakable_cudagraph ¶
Breakable CUDA graph capture/replay.
This is an alternative to :class:CUDAGraphWrapper that replaces vLLM's torch.compile-based FX graph splitting with runtime stream-capture breaks.
The idea (inspired by sgl-project/sglang#19102): instead of pre-splitting the model into many pieces at attention boundaries, a single capture context drives the whole forward and intercepts attention / kv-cache custom ops at the dispatcher to end the current stream capture, run the op eagerly, and resume capture.
The captured artifact is a list of zero-arg callables -- the bound CUDAGraph.replay for graph segments, or the user fn for eager segments -- replayed in order at inference time.
Eager segments must operate on the same static buffers used during capture so subsequent graph segments read the same memory addresses.
BreakableCUDAGraphCapture ¶
Stream-capture context that supports eager breaks via :meth:add_eager.
Usage::
cap = BreakableCUDAGraphCapture(pool=...)
with cap:
output = model(*static_inputs)
# Later, after copying new inputs into the static buffers:
cap.replay()
# Output tensors live at the same addresses as during capture.
Thread-local: only one capture may be active per thread.
Source code in vllm/compilation/breakable_cudagraph.py
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 | |
add_eager ¶
End the current capture segment, run fn eagerly on the capture stream, record fn for replay, and start a new segment.
Returns whatever fn returned during this (capture-time) call. Replay does not return values; callers should propagate any downstream dependencies via static output buffers.
Source code in vllm/compilation/breakable_cudagraph.py
BreakableCUDAGraphWrapper ¶
Drop-in replacement for :class:CUDAGraphWrapper that uses :class:BreakableCUDAGraphCapture instead of a single monolithic torch.cuda.graph() capture.
Same dispatch contract as CUDAGraphWrapper: * If no forward_context is available, run the underlying callable eagerly. * If runtime mode mismatch / NONE, run eagerly. * Otherwise, lazily capture per batch_descriptor and replay on subsequent invocations with the same descriptor.
Source code in vllm/compilation/breakable_cudagraph.py
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 | |
_collect_tensor_addresses staticmethod ¶
Flatten tensor data_ptrs from positional and keyword args in a stable order (positionals first, then kwargs in insertion order).
Used for the DEBUG-mode address-stability check; covers both call styles since vLLM models are typically invoked with kwargs.
Source code in vllm/compilation/breakable_cudagraph.py
eager_break_during_capture ¶
Decorator that turns a custom-op Python kernel into a "break point" for the breakable cudagraph capture.
When the decorated function is invoked outside of a :class:BreakableCUDAGraphCapture context, it executes normally.
When invoked inside a capture context, it ends the current cudagraph segment, runs the function eagerly on the capture stream, records the callable for replay, and starts a fresh segment.
In-place output buffer required. Decorated ops must write into a caller-provided output tensor; a fresh tensor returned by fn would change address each replay and break downstream graph segments.
Decorator order matters. Apply as the outermost decorator if there are other decorators that introduce host-side side effects around the call -- the canonical example is @maybe_transfer_kv_layer for PD-disaggregation, whose wait_for_layer_load and save_kv_layer calls must run in the eager segment, not inside the captured cudagraph. Putting @eager_break_during_capture inside such a decorator would record those side effects into the graph and hang on replay.
The correct order is::
@eager_break_during_capture # outermost
@maybe_transfer_kv_layer
def unified_attention_with_output(...):
...