diff options
| author | Michael S. Tsirkin <mst@redhat.com> | 2015-11-23 12:48:52 +0200 |
|---|---|---|
| committer | Michael S. Tsirkin <mst@redhat.com> | 2015-11-25 13:42:38 +0200 |
| commit | c61f09ed855b5009f816242ce281fd01586d4646 (patch) | |
| tree | 4885044e0e45d871d21fec0321a75f8bcd1d15b1 /docs | |
| parent | d39c87d70763f2755d1d7a719817b06f0281fb01 (diff) | |
vhost-user: clarify start and enable
It seems that we currently have some duplication between
started and enabled states.
The actual reason is that enable is not documented correctly:
what it does is connecting ring to the backend.
This is important for MQ, because a Linux guest expects TX
packets to be completed even if it disables some queues
temporarily.
Cc: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: Victor Kaplansky <victork@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/specs/vhost-user.txt | 20 |
1 files changed, 15 insertions, 5 deletions
diff --git a/docs/specs/vhost-user.txt b/docs/specs/vhost-user.txt index 7b9cd6d0dd..0312d40af0 100644 --- a/docs/specs/vhost-user.txt +++ b/docs/specs/vhost-user.txt @@ -148,13 +148,23 @@ a feature bit was dedicated for this purpose: Starting and stopping rings ---------------------- -Client must only process each ring when it is both started and enabled. +Client must only process each ring when it is started. + +Client must only pass data between the ring and the +backend, when the ring is enabled. + +If ring is started but disabled, client must process the +ring without talking to the backend. + +For example, for a networking device, in the disabled state +client must not supply any new RX packets, but must process +and discard any TX packets. If VHOST_USER_F_PROTOCOL_FEATURES has not been negotiated, the ring is initialized in an enabled state. If VHOST_USER_F_PROTOCOL_FEATURES has been negotiated, the ring is initialized -in a disabled state. Client must not process it until ring is enabled by +in a disabled state. Client must not pass data to/from the backend until ring is enabled by VHOST_USER_SET_VRING_ENABLE with parameter 1, or after it has been disabled by VHOST_USER_SET_VRING_ENABLE with parameter 0. @@ -166,7 +176,7 @@ descriptor is readable) on the descriptor specified by VHOST_USER_SET_VRING_KICK, and stop ring upon receiving VHOST_USER_GET_VRING_BASE. -While processing the rings (when they are started and enabled), client must +While processing the rings (whether they are enabled or not), client must support changing some configuration aspects on the fly. Multiple queue support @@ -309,11 +319,11 @@ Message types Id: 4 Master payload: N/A - This is no longer used. Used to be sent to request stopping + This is no longer used. Used to be sent to request disabling all rings, but some clients interpreted it to also discard connection state (this interpretation would lead to bugs). It is recommended that clients either ignore this message, - or use it to stop all rings. + or use it to disable all rings. * VHOST_USER_SET_MEM_TABLE |