summaryrefslogtreecommitdiffstats
path: root/virt/kvm
diff options
context:
space:
mode:
authorAlex Elder2012-06-21 04:53:53 +0200
committerSage Weil2012-07-06 06:14:22 +0200
commitd65c9e0b9eb43d14ece9dd843506ccba06162ee7 (patch)
tree9705e30834dbd2bad64ca69b815467161c2838f8 /virt/kvm
parentlibceph: don't change socket state on sock event (diff)
downloadkernel-qcow2-linux-d65c9e0b9eb43d14ece9dd843506ccba06162ee7.tar.gz
kernel-qcow2-linux-d65c9e0b9eb43d14ece9dd843506ccba06162ee7.tar.xz
kernel-qcow2-linux-d65c9e0b9eb43d14ece9dd843506ccba06162ee7.zip
libceph: just set SOCK_CLOSED when state changes
When a TCP_CLOSE or TCP_CLOSE_WAIT event occurs, the SOCK_CLOSED connection flag bit is set, and if it had not been previously set queue_con() is called to ensure con_work() will get a chance to handle the changed state. con_work() atomically checks--and if set, clears--the SOCK_CLOSED bit if it was set. This means that even if the bit were set repeatedly, the related processing in con_work() only gets called once per transition of the bit from 0 to 1. What's important then is that we ensure con_work() gets called *at least* once when a socket close event occurs, not that it gets called *exactly* once. The work queue mechanism already takes care of queueing work only if it is not already queued, so there's no need for us to call queue_con() conditionally. So this patch just makes it so the SOCK_CLOSED flag gets set unconditionally in ceph_sock_state_change(). Signed-off-by: Alex Elder <elder@inktank.com> Reviewed-by: Sage Weil <sage@inktank.com>
Diffstat (limited to 'virt/kvm')
0 files changed, 0 insertions, 0 deletions