agentleFS
vllm-projectvllm-project/vllm/csrc/AGENTS.md

vllm / csrc

AGENTS.md97k starsChanged yesterdayApache-2.0View on GitHub

- A .cu is one unit of build parallelism, and it is compiled once per GPU architecture (-gencode on CUDA, --offload-arch on ROCm), so a file instantiating every variant of an op can be the build's whole critical path. Before adding instantiations, find the slowest unit of a cold build from .ninja_log (end minus start per object, MAX_JOBS fixed). - Split on the instantiation axis (head size, output width, dtype, block size), never on line count: kernels in an include-only…

Trending

More talk lately.about the whole repository

Dec 2025: 3 mentionsJan 2026: 4 mentionsFeb 2026: 3 mentionsMar 2026: 3 mentionsApr 2026: 4 mentionsMay 2026: 3 mentionsJun 2026: 2 mentionsJul 2026: 0 mentionsAug 2026: 3 mentionsSep 2026: 4 mentionsOct 2026: 12 mentionsNov 2026: 2 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the vllm-project/vllm repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about vllm-project/vllm

The biggest 5 of 98 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 98

Talked about on GitHub, YouTube, Hacker News, Bluesky, the web and Stack Overflow (98 times).

On GitHub · 28

23 more on GitHub

On YouTube · 21

16 more on YouTube

On Hacker News · 15

10 more on Hacker News

On Bluesky · 15

10 more on Bluesky

On the web · 10

5 more on the web

The file

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before adding instantiations, find the slowest unit of a cold build from .ninja_log (end minus start per object, MAX_JOBS fixed).

    line 6

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

csrc

  • A .cu is one unit of build parallelism, and it is compiled once per GPU architecture (-gencode on CUDA, --offload-arch on ROCm), so a file instantiating every variant of an op can be the build's whole critical path. Before adding instantiations, find the slowest unit of a cold build from .ninja_log (end minus start per object, MAX_JOBS fixed).
  • Split on the instantiation axis (head size, output width, dtype, block size), never on line count: kernels in an include-only header, one thin .cu per variant, and an entry-point unit that only declares and dispatches, so every entry it declares is defined in a variant unit. Keep <torch/all.h> out of kernel headers. Copy an existing split in csrc/ and its CMake wiring, including the arch-gated source list of the file it came from.
  • Never vary a shared function body with a per-unit #define. Identical symbol names with different bodies are an ODR violation, and the linker keeps one copy, so the other variants silently run the wrong code or fail: give each variant its own symbol instead. Derive the variant list, the dispatch arms and the CMake sources from one place, generating them where you can so no unit compiles without a dispatch arm.
  • Call every variant from one test, and measure cold. A build-time claim needs ccache off, MAX_JOBS fixed, before and after, naming the unit that was the critical path: a split only pays off once its unit is, or is about to become, that path, and a compiler flag is no substitute without a measurement.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.