From: "Andrew J. Bennieston" <andrew.bennieston@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: "Andrew J. Bennieston" <andrew.bennieston@citrix.com>,
--cc=paul.durrant@citrix.com, wei.liu2@citrix.com,
ian.campbell@citrix.com, david.vrabel@citrix.com
Subject: [PATCH] netif.h: Document xen-net{back, front} multi-queue feature
Date: Mon, 17 Feb 2014 18:01:50 +0000 [thread overview]
Message-ID: <1392660110-3190-1-git-send-email-andrew.bennieston@citrix.com> (raw)
From: "Andrew J. Bennieston" <andrew.bennieston@citrix.com>
Document the multi-queue feature in terms of XenStore keys to be written
by the backend and by the frontend.
Signed-off-by: Andrew J. Bennieston <andrew.bennieston@citrix.com>
---
xen/include/public/io/netif.h | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/xen/include/public/io/netif.h b/xen/include/public/io/netif.h
index d7fb771..90be2fc 100644
--- a/xen/include/public/io/netif.h
+++ b/xen/include/public/io/netif.h
@@ -69,6 +69,27 @@
*/
/*
+ * Multiple transmit and receive queues:
+ * If supported, the backend will write "multi-queue-max-queues" and set its
+ * value to the maximum supported number of queues.
+ * Frontends that are aware of this feature and wish to use it can write the
+ * key "multi-queue-num-queues", set to the number they wish to use.
+ *
+ * Queues replicate the shared rings and event channels, and
+ * "feature-split-event-channels" is required when using multiple queues.
+ *
+ * For frontends requesting just one queue, the usual event-channel and
+ * ring-ref keys are written as before, simplifying the backend processing
+ * to avoid distinguishing between a frontend that doesn't understand the
+ * multi-queue feature, and one that does, but requested only one queue.
+ *
+ * Frontends requesting two or more queues must not write the toplevel
+ * event-channel and ring-ref keys, instead writing them under sub-keys having
+ * the name "queue-N" where N is the integer ID of the queue for which those
+ * keys belong. Queues are indexed from zero.
+ */
+
+/*
* "feature-no-csum-offload" should be used to turn IPv4 TCP/UDP checksum
* offload off or on. If it is missing then the feature is assumed to be on.
* "feature-ipv6-csum-offload" should be used to turn IPv6 TCP/UDP checksum
--
1.7.10.4
next reply other threads:[~2014-02-17 18:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 18:01 Andrew J. Bennieston [this message]
2014-02-17 18:06 ` [PATCH] netif.h: Document xen-net{back, front} multi-queue feature David Vrabel
2014-02-19 11:06 ` Ian Campbell
2014-02-19 11:47 ` Andrew Bennieston
2014-02-19 12:02 ` Ian Campbell
2014-02-20 10:58 ` Andrew Bennieston
2014-02-20 11:04 ` Ian Campbell
2014-02-21 10:10 ` Paul Durrant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1392660110-3190-1-git-send-email-andrew.bennieston@citrix.com \
--to=andrew.bennieston@citrix.com \
--cc=--cc=paul.durrant@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).