mirror of
https://github.com/rust-vmm/vhost-device.git
synced 2026-01-08 20:57:35 +00:00
a1e013286f
Having all the workspace crates under the crates/ directory is unnecessary. Rust documentation itself recommends all crates to be in the root directory: https://doc.rust-lang.org/book/ch14-03-cargo-workspaces.html#creating-the-second-package-in-the-workspace I paste the text content here, in case the online page ever changes or becomes unavailable: ## Creating the Second Package in the Workspace Next, let’s create another member package in the workspace and call it add_one. Change the top-level Cargo.toml to specify the add_one path in the members list: Filename: Cargo.toml [workspace] members = [ "adder", "add_one", ] Then generate a new library crate named add_one: $ cargo new add_one --lib Created library `add_one` package Your add directory should now have these directories and files: ├── Cargo.lock ├── Cargo.toml ├── add_one │ ├── Cargo.toml │ └── src │ └── lib.rs ├── adder │ ├── Cargo.toml │ └── src │ └── main.rs └── target Signed-off-by: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
40 lines
1.7 KiB
Markdown
40 lines
1.7 KiB
Markdown
# vhost-device-scsi architecture
|
|
|
|
Rough outline of the different pieces and how they fit together:
|
|
|
|
## `scsi/mod.rs`
|
|
|
|
This defines the `Target` trait, which represents a SCSI target. The code in
|
|
this file is independent from:
|
|
|
|
- A particular SCSI implementation: Currently, we have one implementation of
|
|
`Target`, which emulates the SCSI commands itself; but future implementations
|
|
could provide pass-through to an iSCSI target or SCSI devices attached to the
|
|
host.
|
|
- A particular SCSI transport: Nothing in `src/scsi/*` knows anything about
|
|
virtio; this is helpful for maintainability, and also allows our SCSI
|
|
emulation code to be reusable as, for example, an iSCSI target. To this end,
|
|
the `Target` trait is generic over a `Read` and `Write` that it uses for SCSI
|
|
data transfer. This makes testing easy: we can just provide a `Vec<u8>` to
|
|
write into.
|
|
|
|
## `scsi/emulation/*.rs`
|
|
|
|
This is the SCSI emulation code, which forms the bulk of the crate. It provides
|
|
`EmulatedTarget`, an implementation of `Target`. `EmulatedTarget`, in turn,
|
|
looks at the LUN and delegates commands to an implementation of `LogicalUnit`.
|
|
In most cases, this will be `BlockDevice`; there's also `MissingLun`, which is
|
|
used for responding to commands to invalid LUNs.
|
|
|
|
Currently, there is no separation between commands defined in the SPC standard
|
|
(commands shared by all device types) and the SBC standard (block-device
|
|
specific commands). If we ever implemented another device type (CD/DVD seems
|
|
most likely), we'd want to separate those out.
|
|
|
|
As noted above, the emulation code knows nothing about virtio.
|
|
|
|
## `src/{main,virtio}.rs`
|
|
|
|
This code handles vhost-user, virtio, and virtio-scsi; it's the only part of
|
|
the crate that knows about these protocols.
|