Hi Dariusz,
On Tue, Aug 22, 2017 at 06:24:52PM +0200, Dariusz Stojaczyk wrote:
When user receives destroy_device signal, he does not know *why* that
event happened. He does not differ between socket shutdown and virtio
processing pause. User could completely delete device during transition
from BIOS to kernel, causing freeze or possibly kernel panic. Instead
of changing new_device/destroy_device callbacks and breaking the ABI,
a set of new functions new_connection/destroy_connection has been added.
Signed-off-by: Dariusz Stojaczyk <dariuszx.stojac...@intel.com>
---
v2: also updated vhost_lib.rst
doc/guides/prog_guide/vhost_lib.rst | 15 +++++++++++++--
lib/librte_vhost/rte_vhost.h | 5 ++++-
lib/librte_vhost/socket.c | 23 +++++++++++++++++++----
3 files changed, 36 insertions(+), 7 deletions(-)
thanks for adding documentation!
I'm still not sure I understand the use case. So just for my
understanding: users need to distinct between "the device is going
away temporarily, keep the connection" and "we're shutting down for good", is
that it?
Maybe it's just me or maybe it means you could explain your example in
the commit message a bit more. I think the code looks sane, so
Reviewed-by: Jens Freimann <jfreim...@redhat.com>
Oh, and you should put the maintainers on Cc to get a faster review.
regards,
Jens
