search for: shutdown_tx

...cross, which I'm not sure if it is by design or a > > > problem is that I can see this sequence coming from the guest (with > > > other activity in between): > > > > > > ? ? 1) OP_SHUTDOWN w/ flags == SHUTDOWN_RX > > > ????2) OP_SHUTDOWN w/ flags == SHUTDOWN_TX > > > ????3) OP_SHUTDOWN w/ flags == SHUTDOWN_TX|SHUTDOWN_RX How did you trigger this sequence? I'd like to reproduce it. > > > I orignally had my backend close things down at #2, however this meant > > > that when #3 arrived it was for a non-existent socket (or, w...

...cross, which I'm not sure if it is by design or a > > > problem is that I can see this sequence coming from the guest (with > > > other activity in between): > > > > > > ? ? 1) OP_SHUTDOWN w/ flags == SHUTDOWN_RX > > > ????2) OP_SHUTDOWN w/ flags == SHUTDOWN_TX > > > ????3) OP_SHUTDOWN w/ flags == SHUTDOWN_TX|SHUTDOWN_RX How did you trigger this sequence? I'd like to reproduce it. > > > I orignally had my backend close things down at #2, however this meant > > > that when #3 arrived it was for a non-existent socket (or, w...

...y seems > fine. > > One wrinkle I came across, which I'm not sure if it is by design or a > problem is that I can see this sequence coming from the guest (with > other activity in between): > > ? ? 1) OP_SHUTDOWN w/ flags == SHUTDOWN_RX > ????2) OP_SHUTDOWN w/ flags == SHUTDOWN_TX > ????3) OP_SHUTDOWN w/ flags == SHUTDOWN_TX|SHUTDOWN_RX > > I orignally had my backend close things down at #2, however this meant > that when #3 arrived it was for a non-existent socket (or, worse, an > active one if the ports got reused). I checked v5 of the spec > proposal[0]...

...y seems > fine. > > One wrinkle I came across, which I'm not sure if it is by design or a > problem is that I can see this sequence coming from the guest (with > other activity in between): > > ? ? 1) OP_SHUTDOWN w/ flags == SHUTDOWN_RX > ????2) OP_SHUTDOWN w/ flags == SHUTDOWN_TX > ????3) OP_SHUTDOWN w/ flags == SHUTDOWN_TX|SHUTDOWN_RX > > I orignally had my backend close things down at #2, however this meant > that when #3 arrived it was for a non-existent socket (or, worse, an > active one if the ports got reused). I checked v5 of the spec > proposal[0]...

...sure if it is by design or a > > > > problem is that I can see this sequence coming from the guest (with > > > > other activity in between): > > > > > > > > 1) OP_SHUTDOWN w/ flags == SHUTDOWN_RX > > > > 2) OP_SHUTDOWN w/ flags == SHUTDOWN_TX > > > > 3) OP_SHUTDOWN w/ flags == SHUTDOWN_TX|SHUTDOWN_RX > > How did you trigger this sequence? I'd like to reproduce it. > Nothing magic. I've written some logging into my backend and captured the result for a simple backend initiated connection. In the log &q...

...> One wrinkle I came across, which I'm not sure if it is by design or a > > problem is that I can see this sequence coming from the guest (with > > other activity in between): > > > > ? ? 1) OP_SHUTDOWN w/ flags == SHUTDOWN_RX > > ????2) OP_SHUTDOWN w/ flags == SHUTDOWN_TX > > ????3) OP_SHUTDOWN w/ flags == SHUTDOWN_TX|SHUTDOWN_RX > > > > I orignally had my backend close things down at #2, however this meant > > that when #3 arrived it was for a non-existent socket (or, worse, an > > active one if the ports got reused). I checked v5 of...

...been using it in my project and it mostly seems fine. One wrinkle I came across, which I'm not sure if it is by design or a problem is that I can see this sequence coming from the guest (with other activity in between): ? ? 1) OP_SHUTDOWN w/ flags == SHUTDOWN_RX ????2) OP_SHUTDOWN w/ flags == SHUTDOWN_TX ????3) OP_SHUTDOWN w/ flags == SHUTDOWN_TX|SHUTDOWN_RX I orignally had my backend close things down at #2, however this meant that when #3 arrived it was for a non-existent socket (or, worse, an active one if the ports got reused). I checked v5 of the spec proposal[0] which says: If these bits...

This series is based on Michael Tsirkin's vhost branch (v4.5-rc6). I'm about to process Claudio Imbrenda's locking fixes for virtio-vsock but first I want to share the latest version of the code. Several people are playing with vsock now so sharing the latest code should avoid duplicate work. v5: * Transport reset event for live migration support * Reorder virtqueues, drop unused

This series is based on Michael Tsirkin's vhost branch (v4.5-rc6). I'm about to process Claudio Imbrenda's locking fixes for virtio-vsock but first I want to share the latest version of the code. Several people are playing with vsock now so sharing the latest code should avoid duplicate work. v5: * Transport reset event for live migration support * Reorder virtqueues, drop unused