[LUDOC-291] make RPC operation packet structure linkable to cross references. Created: 11/Jun/15 Updated: 21/Sep/16 Resolved: 21/Sep/16 |
|
| Status: | Resolved |
| Project: | Lustre Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Richard Henwood (Inactive) | Assignee: | Lustre Manual Triage |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
I.e. make the figure at the bottom of pg 50 here: https://build.hpdd.intel.com/job/lustre-protocol-reviews/29/artifact/protocol.pdf contain hyperlinks to the existing definitions of 'ptlrpc_body' etc. |
| Comments |
| Comment by Gerrit Updater [ 11/Jun/15 ] |
|
Richard Henwood (richard.henwood@intel.com) uploaded a new patch: http://review.whamcloud.com/15229 |
| Comment by Andrew Uselton (Inactive) [ 13/Jun/15 ] |
|
The table mechanism seems like it does a reasonable job for laying out the packet structure. Do you have any ideas for how to make the structure definitions similarly crisp? One thing we'll want to investigate is what the table approach looks like when the packet structure is too long to fit all on a single line. |
| Comment by Gerrit Updater [ 17/Jun/15 ] |
|
Richard Henwood (richard.henwood@intel.com) uploaded a new patch: http://review.whamcloud.com/15329 |
| Comment by Gerrit Updater [ 19/Jun/15 ] |
|
Richard Henwood (richard.henwood@intel.com) uploaded a new patch: http://review.whamcloud.com/15360 |