Skip to content

docs: add external byte stream proposal - #1791

Open
andreiltd wants to merge 2 commits into
hyperlight-dev:mainfrom
andreiltd:tandr/hip-ext-bufs
Open

docs: add external byte stream proposal#1791
andreiltd wants to merge 2 commits into
hyperlight-dev:mainfrom
andreiltd:tandr/hip-ext-bufs

Conversation

@andreiltd

Copy link
Copy Markdown
Member

Signed-off-by: Tomasz Andrzejak <andreiltd@gmail.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

Changes are documentation-only and the identified issues are minor wording/clarity nits with straightforward fixes.

Pull request overview

Adds HIP 0002 proposal documentation describing a wire format that keeps message structure in a FlatBuffer “envelope” while carrying large payload bytes in an ordered external byte stream immediately following the envelope, to avoid intermediate copies (notably for virtq scatter/gather).

Changes:

  • Document the motivation and wire layout for a FlatBuffer envelope + external byte stream design.
  • Specify serialization/consumption semantics and validation requirements for external bytes.
  • Note relationship/inspiration from Apache Arrow IPC buffer descriptors.
File summaries
File Description
proposals/0002-envelope-external-byte-stream/README.md New proposal document defining the envelope + external byte stream approach, including semantics and validation requirements.
Review details

Suppressed comments (2)

proposals/0002-envelope-external-byte-stream/README.md:13

  • Hyphenate the compound modifier "format-independent" for correct grammar.
of writing. The optimization is format independent and applies wherever serialized metadata can

proposals/0002-envelope-external-byte-stream/README.md:81

  • Hyphenate "protocol-defined" here (and keep usage consistent) since it is a compound modifier for "order".
The external bytes are consumed in protocol defined order. For function call parameters, this can be
  • Files reviewed: 1/1 changed files
  • Comments generated: 2
  • Review effort level: Lite

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

Comment thread proposals/0002-envelope-external-byte-stream/README.md Outdated
Comment thread proposals/0002-envelope-external-byte-stream/README.md
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Signed-off-by: Tomasz Andrzejak <andreiltd@users.noreply.github.com>

@ludfjig ludfjig left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice

@github-actions github-actions Bot removed the ready-for-review PR is ready for (re-)review label Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants