mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2025-02-05 18:20:34 +00:00
67dc513aa1
The max_read and max_write in worker::start_message_loop are confusing. The max_read defines the amount of data the filesystem should be fed / read from /def/fuse, during the write(2) operation to the filesystem. The meaning is oppposite to the mount option max_read, which is for the actual read operation. This change adds API doc, fix the new API, and renames variables to disambiguate them. With the new API, the meaning should be more intuitive and consistent. Bug: 220386264 Test: use in Android Change-Id: Ifa77cb3c291626fdbb8a28f36cf2a44dd859f70f Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3526527 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Victor Hsieh <victorhsieh@chromium.org> |
||
|---|---|---|
| .. | ||
| filesystem.rs | ||
| fuzzing.rs | ||
| lib.rs | ||
| mount.rs | ||
| server.rs | ||
| sys.rs | ||
| worker.rs | ||