> I started this manual page to explain how tmpfs works overall, the
> design decisions taken in its development, etc.  And in order to explain
> many things, I had to detail its structures.  I think it can work well, as it
> can explain many more things than a single comment in the file...
> 
> FWIW, we already describe structures in manual pages, e.g., vnode(9).

it makes sense for interface descriptions like vnode(9).
and it might make sense for high-level design explanation.

however, in this case, what we are talking about are merely
implementation details.
IMO, having comments near the code is better,
especially for immature and changing code like this.

YAMAMOTO Takashi