From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wei Liu Subject: [PATCH] netif: document feature-split-event-channel Date: Wed, 22 May 2013 10:50:39 +0100 Message-ID: <1369216239-11211-1-git-send-email-wei.liu2@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org Cc: Keir Fraser , Wei Liu , Ian Campbell , Jan Beulich List-Id: xen-devel@lists.xenproject.org This is a new feature to separate TX and RX notification. Document it in canonical header for future reference. For reference implementation, please see Xen network driver in Linux kernel. Signed-off-by: Wei Liu Cc: Ian Campbell Cc: Keir Fraser Cc: Jan Beulich --- xen/include/public/io/netif.h | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/xen/include/public/io/netif.h b/xen/include/public/io/netif.h index 9664998..bed0e7f 100644 --- a/xen/include/public/io/netif.h +++ b/xen/include/public/io/netif.h @@ -57,6 +57,18 @@ */ /* + * "feature-split-event-channels" is introduced to separate guest TX + * and RX notificaion. Backend either doesn't support this feature or + * advertise it via xenstore as 0 (disabled) or 1 (enabled). + * + * To make use of this feature, frontend should allocate two event + * channels for TX and RX, advertise them to backend as + * "event-channel-tx" and "event-channel-rx" respectively. If frontend + * doesn't want to use this feature, it just writes "event-channel" + * node as before. + */ + +/* * This is the 'wire' format for packets: * Request 1: netif_tx_request -- NETTXF_* (any flags) * [Request 2: netif_tx_extra] (only if request 1 has NETTXF_extra_info) -- 1.7.10.4