Repository navigation
docs: decide the engine, netlink, the comparison of backends and ECN for release 0.4 - #133
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Decisions D-098 to D-103 for release 0.4, with the four spikes behind them (the data path of the engine, netlink by a layer of our own, the same link on the kernel and on the engine, ECN), the ledger rows and matrix cells they change, and an input
only_enginefor the workflowSpikes.Worth a look: the engine has one small module with
unsafe(D-098; nothing safe can bind a packet socket today), its timer isautoand can be set (D-098), and the engine backend is a mode of the Kernel backend with one new crate,netscenario-engine, which needs its name taken on crates.io before the tag of 0.4. No code of the product changes.