Wei Liu
2013-May-22 16:34 UTC
[PATCH net-next 0/2 V3] Xen network: split event channels support
This series adds a new feature called split event channels. In the original implementation, only one event channel is setup between frontend and backend. This is not ideal as TX notification interferes with RX notification. Using dedicated event channels for TX and RX solves this issue. Changes since V2: * feature_split_event_channels -> separate_tx_rx_irq * make separate_tx_rx_irq bool * document this feature in header file * don''t report fatal if writing feature to xenstore fails * frontend will fall back to single event channel if new feature setup fails Changes since V1: * change subject lines of commits to be more specific * add parameter feature_split_event_channels for xen-netback * remove two dev_info Wei Liu (3): xen-netback: split event channels support for Xen backend driver xen-netfront: split event channels support for Xen frontend driver xen: netif.h: document feature-split-event-channels drivers/net/xen-netback/common.h | 13 ++- drivers/net/xen-netback/interface.c | 85 ++++++++++++++--- drivers/net/xen-netback/netback.c | 14 ++- drivers/net/xen-netback/xenbus.c | 41 ++++++-- drivers/net/xen-netfront.c | 178 +++++++++++++++++++++++++++++------ include/xen/interface/io/netif.h | 12 +++ 6 files changed, 285 insertions(+), 58 deletions(-) -- 1.7.10.4
David Miller
2013-May-24 01:41 UTC
Re: [PATCH net-next 0/2 V3] Xen network: split event channels support
From: Wei Liu <wei.liu2@citrix.com> Date: Wed, 22 May 2013 17:34:44 +0100> This series adds a new feature called split event channels. > > In the original implementation, only one event channel is setup between > frontend and backend. This is not ideal as TX notification interferes with RX > notification. Using dedicated event channels for TX and RX solves this issue.Series applied, thanks.