Re: [dpdk-dev] [PATCH v2] vhost: added user callbacks for socket open/close

2017-08-29 Thread Jens Freimann
On Tue, Aug 29, 2017 at 06:08:45AM +, Stojaczyk, DariuszX wrote: Hi Jens, 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?

Re: [dpdk-dev] [PATCH v2] vhost: added user callbacks for socket open/close

2017-08-28 Thread Stojaczyk, DariuszX
Hi Jens, > 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? Yes, exactly. > Maybe it's just me or maybe it means you could e

Re: [dpdk-dev] [PATCH v2] vhost: added user callbacks for socket open/close

2017-08-25 Thread Jens Freimann
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

[dpdk-dev] [PATCH v2] vhost: added user callbacks for socket open/close

2017-08-22 Thread Dariusz Stojaczyk
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_d