aboutsummaryrefslogtreecommitdiffstats
path: root/net/packet
diff options
context:
space:
mode:
authorPaul Durrant <pdurrant@amazon.com>2019-12-23 09:59:23 +0000
committerDavid S. Miller <davem@davemloft.net>2019-12-26 15:16:26 -0800
commit9476654bd5e8ad42abe8ee9f9e90069ff8e60c17 (patch)
treed063572a1f27c26bb642e0fb30a5afe50ba5afb4 /net/packet
parentMerge branch 'RTL8211F-RGMII-RX-TX-delay-configuration-improvements' (diff)
downloadlinux-dev-9476654bd5e8ad42abe8ee9f9e90069ff8e60c17.tar.xz
linux-dev-9476654bd5e8ad42abe8ee9f9e90069ff8e60c17.zip
xen-netback: support dynamic unbind/bind
By re-attaching RX, TX, and CTL rings during connect() rather than assuming they are freshly allocated (i.e. assuming the counters are zero), and avoiding forcing state to Closed in netback_remove() it is possible for vif instances to be unbound and re-bound from and to (respectively) a running guest. Dynamic unbind/bind is a highly useful feature for a backend module as it allows it to be unloaded and re-loaded (i.e. updated) without requiring domUs to be halted. This has been tested by running iperf as a server in the test VM and then running a client against it in a continuous loop, whilst also running: while true; do echo vif-$DOMID-$VIF >unbind; echo down; rmmod xen-netback; echo unloaded; modprobe xen-netback; cd $(pwd); brctl addif xenbr0 vif$DOMID.$VIF; ip link set vif$DOMID.$VIF up; echo up; sleep 5; done in dom0 from /sys/bus/xen-backend/drivers/vif to continuously unbind, unload, re-load, re-bind and re-plumb the backend. Clearly a performance drop was seen but no TCP connection resets were observed during this test and moreover a parallel SSH connection into the guest remained perfectly usable throughout. Signed-off-by: Paul Durrant <pdurrant@amazon.com> Reviewed-by: Wei Liu <wei.liu@kernel.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/packet')
0 files changed, 0 insertions, 0 deletions