vmsilo fork of vhost rust libraries
a0d7fb9200
By adding a "thread_id" parameter to handle_event(), the backend crate can now indicate to the backend implementation which thread triggered the processing of some events. This is applied to vhost-user-net backend and allows for simplifying a lot the code since each thread is identical. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> |
||
|---|---|---|
| src | ||
| .gitmodules | ||
| Cargo.toml | ||
| CODEOWNERS | ||
| coverage_config.json | ||
| LICENSE-APACHE | ||
| README.md | ||
Crate Name
Design
TODO: This section should have a high-level design of the crate.
Some questions that might help in writing this section:
- What is the purpose of this crate?
- What are the main components of the crate? How do they interact which each other?
Usage
TODO: This section describes how the crate is used.
Some questions that might help in writing this section:
- What traits do users need to implement?
- Does the crate have any default/optional features? What is each feature doing?
- Is this crate used by other rust-vmm components? If yes, how?
Examples
TODO: Usage examples.
use my_crate;
...
License
!!!NOTICE: The BSD-3-Clause license is not included in this template. The license needs to be manually added because the text of the license file also includes the copyright. The copyright can be different for different crates. If the crate contains code from CrosVM, the crate must add the CrosVM copyright which can be found here. For crates developed from scratch, the copyright is different and depends on the contributors.