From: Paul Durrant <paul.durrant@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Paul Durrant <paul.durrant@citrix.com>
Subject: [PATCH 2/4] public/io/netif.h: add definition of gso_prefix flag
Date: Fri, 16 Oct 2015 13:36:20 +0100 [thread overview]
Message-ID: <1444998982-23881-3-git-send-email-paul.durrant@citrix.com> (raw)
In-Reply-To: <1444998982-23881-1-git-send-email-paul.durrant@citrix.com>
This flag is defined here only for compatibility with the Linux variant of
this header. The feature has never been documented and should be
considered deprecated.
Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
---
xen/include/public/io/netif.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/xen/include/public/io/netif.h b/xen/include/public/io/netif.h
index 0fd413a..57eb903 100644
--- a/xen/include/public/io/netif.h
+++ b/xen/include/public/io/netif.h
@@ -402,6 +402,10 @@ typedef struct netif_rx_request netif_rx_request_t;
#define _NETRXF_extra_info (3)
#define NETRXF_extra_info (1U<<_NETRXF_extra_info)
+/* Packet has GSO prefix. Deprecated but included for compatibility */
+#define _NETRXF_gso_prefix (4)
+#define NETRXF_gso_prefix (1U<<_NETRXF_gso_prefix)
+
struct netif_rx_response {
uint16_t id;
uint16_t offset; /* Offset in page of start of received packet */
--
2.1.4
next prev parent reply other threads:[~2015-10-16 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 12:36 [PATCH 0/4] Updates to public/io/netif.h Paul Durrant
2015-10-16 12:36 ` [PATCH 1/4] public/io/netif.h: document the reality of netif_rx_request/reponse id Paul Durrant
2015-10-16 12:36 ` Paul Durrant [this message]
2015-10-16 12:36 ` [PATCH 3/4] public/io/netif.h: add documentation for hash negotiation and mapping Paul Durrant
2015-10-16 12:36 ` [PATCH 4/4] public/io/netif.h: add extra info slots for passing hash values Paul Durrant
2015-10-16 12:37 ` [PATCH 0/4] Updates to public/io/netif.h 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=1444998982-23881-3-git-send-email-paul.durrant@citrix.com \
--to=paul.durrant@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).