RN vs HN Question

Module 19 · Chapter 19.3 · CHI Interview Mastery

Project thread — 19.2 named the roles. 19.3 contrasts RN and HN; 19.4 zooms into the directory.

1. The Question

"What's the difference between a request node and a home node?" — or: "Compare RN and HN," "Who decides coherence, the RN or the HN?" "Why do we need a home node at all if request nodes have caches?" It is a standard intermediate question that separates candidates who memorized labels (19.2) from those who understand the division of responsibility.

2. What the Interviewer Is Probing

This question tests whether you understand where authority lives in CHI. The interviewer wants to see:

• Do you frame the contrast correctly — client vs coordinator, not two similar things?
• Do you know the home is the decision point — it orders, tracks, and snoops?
• Do you understand the asymmetry — the home is an authority; requesters funnel through it?
• Can you explain why the home exists — the single per-address serialization/tracking point?

A candidate who describes them as symmetric peers ("both handle coherence") reveals they miss the coordinator-vs-client structure that is the essence of a directory protocol.

3. Key Terms

4. Where This Sits in the Interview

This is the third rung — from naming roles (19.2) to understanding their relationship of authority. It is the pivot to the coherence-mechanism questions: the directory (19.4), ownership transfer (19.5), and flows (19.6) all rest on the home being the decision point. If you frame RN-vs-HN as client-vs-coordinator cleanly, those flows follow naturally; if you flatten them into peers, the flows become confusing.

It deepens 19.2's roles into a contrast, and it directly sets up 19.4: the reason the home is the coordinator is that it owns the directory. The insight you deliver here — the home is the single per-address authority — is the thread that runs through the entire coherence half of the interview.

5. The Core Answer

The one-line contrast, and the asymmetry:

"The request node is where coherence is consumed — a client that caches lines and issues requests; the home node is where coherence is decided — the coordinator that orders transactions, tracks sharers, and issues snoops. In short: the RN asks, the HN decides."

The division of responsibility:

• RN — the client. Holds lines in its cache, initiates reads and writes, and participates in coherence by responding to snoops and obeying the states the home grants.
• HN — the authority. For its addresses, it is the single serialization point: it orders transactions, owns the directory of sharers, and issues the snoops that enforce coherence.
• The asymmetry. They are not symmetric peers. Many request nodes funnel through one home node per address — which is precisely what gives coherence a single ordering and tracking point.

The synthesis:

The RN and HN differ as client and coordinator: the RN consumes coherence (caches, asks, obeys), the HN decides it (orders, tracks, snoops). The one-liner is "the RN asks; the HN decides." The distinguishing insight is the asymmetry — many RNs, one HN per address — so the home is the authority that serializes and tracks, not a peer of the requester.

6. Structuring Your Answer

The template for the contrast:

• 1. The one-line contrast. "RN consumes coherence, HN decides it — the RN asks, the HN decides." Lead with the frame.
• 2. RN responsibilities. Caches, initiates, responds to snoops, obeys grants — a client.
• 3. HN responsibilities. Orders, tracks (directory), snoops — a coordinator/authority.
• 4. The asymmetry and why. Many RNs, one HN per address → the single serialization/tracking point → that's why the home exists.

The point to carry:

The frame — consumer vs decider — must come first, because it organizes everything after. Two lists of responsibilities without the frame read as "here are things each does"; the consumer-vs-decider framing turns them into complementary roles in a division of authority. And close with the asymmetry (many RNs, one HN), because that is the why — it explains the home's existence as the single per-address ordering point.

7. The Answer Skeleton

The contrast in a table — the shape to have ready.

The rule to carry: the count row is the punchline. "Many RNs, one HN per address" captures the asymmetry that everything else follows from — the home is the single point where a line's transactions are ordered and its sharers tracked. Lead the contrast with roles, but land it on the asymmetry.

8. The Model Answer

A full, polished answer:

"The cleanest way to put it: the request node is where coherence is consumed, and the home node is where coherence is decided — the RN asks, the HN decides.

A request node is a client. It holds lines in its cache, initiates reads and writes, and participates in coherence — it responds to snoops and obeys the states the home grants it. But it doesn't decide anything about the global picture.

A home node is the coordinator and the authority for a range of addresses. It's the single serialization point — it orders all transactions to those addresses, it owns the directory that tracks which caches share each line, and it issues the snoops that enforce coherence.

The key is that they're not symmetric. Many request nodes funnel through one home node per address — and that's exactly the point: coherence needs a single place per line to order transactions and track sharers, and that place is the home. So: the RN asks, the HN decides."

That is the frame (consumer/decider), the two role descriptions, and the asymmetry as the closing insight — with "the RN asks, the HN decides" bookending it for memorability.

9. The Depth Ladder

Matching depth to the role.

• Junior signal. "The RN makes requests and the HN is the home for them." — correct but flat; no authority/coordination structure.
• Mid signal. Adds the responsibilities — "the RN caches and responds to snoops; the HN orders transactions and has the directory." Shows the division of labor.
• Senior signal. Adds the asymmetry and why — "the home is the single serialization point per address; many requesters funnel through it, which is what gives coherence a consistent order and a place to track sharers." Connects the role to the mechanism.
• Staff signal. Adds the scaling nuance — "you distribute the home across many HNs by address interleaving, so there's one HN per address but many HNs per system — that's how the coordinator role scales without becoming a bottleneck." Shows system-design judgment.

The point to carry:

Climb by explaining the single-serialization-point role of the home and then how it scales (one HN per address, many HNs by interleaving). That takes you from "the HN coordinates" (mid) to "the HN is the per-address authority, distributed for scale" (staff) — connecting this question to scalability (19.1) and foreshadowing the large-SoC question (19.10).

10. A Concrete Example

The example that grounds the contrast:

"Concretely: two cores, both request nodes, both want to write the same line. If they were symmetric peers, who orders their writes? Nobody — they'd race. In CHI, both funnel through the same home node for that address, and the home orders them — one first, one second — snooping between them. That's the asymmetry in action: the requesters ask, and the home decides the order. Remove the home and you've removed the thing that makes concurrent writes to one line well-defined."

A two-writer scenario shows why the home must be an authority, not a peer: without a single ordering point, concurrent same-line accesses have no defined order — which is the whole reason the coordinator role exists.

11. Mental Map

The recall structure — two columns and a punchline.

• RN = client: caches, asks, obeys. → "consumes coherence."
• HN = coordinator: orders, tracks, snoops. → "decides coherence."
• Asymmetry (the punchline): many RNs → one HN per address → "the single serialization/tracking point."
• One-liner: the RN asks; the HN decides.

The rule to carry: hold the contrast as consumer-vs-decider, and always end on the asymmetry. The two columns are the roles; the many-to-one relationship is the insight. If you deliver only the columns, you've described two jobs; adding the asymmetry explains the architecture.

12. What a Strong Answer Includes

The rubric.

The rule to carry: the asymmetry is the highest-value element. Describing responsibilities is mid-level; explaining that the home is the single per-address authority that requesters funnel through — and why that is necessary for a defined order — is what reads as senior. Always land the answer there.

13. Weak Answer vs Strong Answer

Same knowledge, two deliveries.

• Weak: "Both the RN and HN handle coherence. The RN makes requests and the HN receives them. They work together to keep caches consistent." — symmetric framing ("both handle coherence," "work together") that misses who decides — no authority structure.
• Strong: "The RN consumes coherence — it caches and asks. The HN decides it — it orders, tracks sharers, and snoops. They're not peers: many RNs funnel through one HN per address, so the home is the single point that orders and tracks. The RN asks; the HN decides." — frame, roles, asymmetry, one-liner.

The difference is authority: the weak answer treats them as collaborators of equal standing; the strong answer identifies the home as the decision-maker and the requesters as clients — the actual structure of a directory protocol.

14. The Interview Trap

15. Common Mistakes

• Symmetric peers. Assumption: both do coherence. Trap: no authority structure. Fix: consumer vs decider.
• "RN does coherence." Assumption: the requester decides. Trap: wrong authority. Fix: the RN participates; the HN decides.
• No asymmetry. Assumption: one-to-one. Trap: misses the serialization point. Fix: many RNs, one HN per address.
• Vague HN role. Assumption: "the home coordinates." Trap: no specifics. Fix: orders, tracks (directory), snoops.
• Forgetting participation. Assumption: the RN only asks. Trap: misses snoop responses. Fix: the RN responds to snoops and obeys grants.
• No scaling note. Assumption: one home. Trap: sounds like a bottleneck. Fix: distributed HNs by interleaving (when asked).

16. Interview Checklist

• Lead with the consumer-vs-decider frame — the RN asks, the HN decides.
• Give the RN role — caches, initiates, responds to snoops, obeys grants.
• Give the HN role — orders, tracks sharers (directory), issues snoops.
• Land on the asymmetry — many RNs, one HN per address.
• Explain why — a single serialization/tracking point per line.
• Note distributed HNs for scale only if depth is wanted.

17. Key Takeaways

• The RN consumes coherence (client); the HN decides it (authority).
• The one-liner: the RN asks, the HN decides.
• The RN caches, initiates, and participates; the HN orders, tracks, and snoops.
• They are not symmetric — many RNs funnel through one HN per address.
• The home is the single serialization/tracking point per line.
• Land the answer on the asymmetry; the guidance here is representative.

18. Quick Revision

RN vs HN. (capsule answer.) "The cleanest contrast: the request node is where coherence is consumed, and the home node is where coherence is decided — the RN asks, the HN decides. A request node is a client: it holds lines in its cache, initiates reads and writes, and participates in coherence by responding to snoops and obeying the states the home grants — but it decides nothing globally. A home node is the coordinator and authority for a range of addresses: it is the single serialization point that orders transactions, owns the directory that tracks which caches share each line, and issues the snoops that enforce coherence. Crucially they are not symmetric peers — many request nodes funnel through one home node per address, which is exactly what gives coherence a single place to order transactions and track sharers. (For scale, the home is distributed across many HNs by address interleaving — one HN per address, many per system.)" Lead with consumer vs decider, give the two roles, and land on the asymmetry. The trap is calling them symmetric peers; authority lives with the home. Representative interview guidance; 19.4 covers the directory the home owns.

Coming Next

Chapter 19.4 — Directory Role Question. The home node's authority comes from the directory; the next question asks you to explain it. Chapter 19.4 covers the directory-role question — why the directory exists, what it stores, how it turns broadcast snooping into targeted snooping, and the crisp answer that connects the directory to CHI's scalability.