[Docs] Describe op to kernel dispatch as kernel interfaces and implementations

[lcy-seso]

Problems

• new-op teaches role, a three-argument kernel_for(role, inputs, call) and an op-level entry_for(role, call). None of those exist; the op→kernel dispatch migration removed them. Its kernel_types keys are invented, and its _eager_forward calls a self._call_spec(...) the base class does not define. It never mentions interfaces, which every op holding kernels now declares.
• backends says kernel_for and entry_for are the op author's and that an op with no in-tree implementation may leave entry_for out. It predates register_implementation, so a backend is offered only a target. Its "why selection has two layers" section says TileOPs does no candidate filtering, which now holds only of the target path.
• torch-compile declares kernel_types and no interfaces in its op skeleton, and calls kernel_for with three arguments.
• manifest calls a composition stage's target a kernel role.

Changes

• new-op gains a kernel-selection section: the two arguments of kernel_for, what a kernel interface is and where it lives, the four declarations an implementation makes (devices / supported_archs, applies / refusal, general / preferred_over, entry_for) with their defaults, and GemmFwdOp's three implementations as the worked example.
• backends gains a section comparing the three ways in — kernel_map= replaces one implementation for one op instance, register_implementation adds an implementation to an interface, a target replaces the whole op — and states for each what it changes, what it acts on, which contract it is written against, and what happens to a call it does not serve.
• Corrected throughout: the error a call raises when no key runs on the device type, when a backend's registration takes effect, gemm_cp_async's refusal of a K row narrower than one four-byte load, and the claim that the protocol has no default target, which the same page contradicts by documenting set_default_target.
• Every code block is copied from TileOPs main and names the file it came from.
• English and Chinese pages change together.

[Copilot]

Copilot review overview

🟡 Changes recommended

The new manifest-family precedence and Sampling-page routing lack focused renderer coverage.

Review effort: Balanced
Findings: 1

Open (1)

• Add test for manifest_family precedence and Sampling page emission · New

What changed in this PR

Updates dispatch documentation to match TileOPs’ current kernel-interface model and extends benchmark rendering for Sampling.

Changes:

• Documents kernel interfaces, implementations, and backend extension paths bilingually.
• Corrects obsolete dispatch examples and terminology.
• Adds manifest-driven Sampling benchmark classification and navigation.

File	Description
scripts/​gen_bench_pages.py	Adds manifest-family routing and Sampling pages.
mkdocs.yml	Adds Sampling navigation translation.
hooks.py	Adds Sampling to benchmark navigation order.
docs/​torch-compile.md	Updates the English dispatch example.
docs/​torch-compile.zh.md	Updates the Chinese dispatch example.
docs/​new-op.md	Documents current kernel selection architecture.
docs/​new-op.zh.md	Chinese counterpart of the new-op updates.
docs/​manifest.md	Replaces obsolete kernel-role terminology.
docs/​manifest.zh.md	Updates corresponding Chinese terminology.
docs/​backends.md	Documents three backend integration mechanisms.
docs/​backends.zh.md	Chinese counterpart of backend guidance.
CLAUDE.md	Refreshes repository development conventions.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.