From: Paul Durrant <paul.durrant@citrix.com>
To: xen-devel@lists.xenproject.org, netdev@vger.kernel.org
Cc: Paul Durrant <paul.durrant@citrix.com>
Subject: [PATCH net-next v4 4/4] xen-netback: use hash value from the frontend
Date: Fri, 13 May 2016 09:37:29 +0100 [thread overview]
Message-ID: <1463128649-20832-5-git-send-email-paul.durrant__31096.1049901836$1463129573$gmane$org@citrix.com> (raw)
In-Reply-To: <1463128649-20832-1-git-send-email-paul.durrant@citrix.com>
My recent patch to include/xen/interface/io/netif.h defines a new extra
info type that can be used to pass hash values between backend and guest
frontend.
This patch adds code to xen-netback to use the value in a hash extra
info fragment passed from the guest frontend in a transmit-side
(i.e. netback receive side) packet to set the skb hash accordingly.
Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
---
drivers/net/xen-netback/netback.c | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/drivers/net/xen-netback/netback.c b/drivers/net/xen-netback/netback.c
index 7c72510..a5b5aad 100644
--- a/drivers/net/xen-netback/netback.c
+++ b/drivers/net/xen-netback/netback.c
@@ -1509,6 +1509,33 @@ static void xenvif_tx_build_gops(struct xenvif_queue *queue,
}
}
+ if (extras[XEN_NETIF_EXTRA_TYPE_HASH - 1].type) {
+ struct xen_netif_extra_info *extra;
+ enum pkt_hash_types type = PKT_HASH_TYPE_NONE;
+
+ extra = &extras[XEN_NETIF_EXTRA_TYPE_HASH - 1];
+
+ switch (extra->u.hash.type) {
+ case _XEN_NETIF_CTRL_HASH_TYPE_IPV4:
+ case _XEN_NETIF_CTRL_HASH_TYPE_IPV6:
+ type = PKT_HASH_TYPE_L3;
+ break;
+
+ case _XEN_NETIF_CTRL_HASH_TYPE_IPV4_TCP:
+ case _XEN_NETIF_CTRL_HASH_TYPE_IPV6_TCP:
+ type = PKT_HASH_TYPE_L4;
+ break;
+
+ default:
+ break;
+ }
+
+ if (type != PKT_HASH_TYPE_NONE)
+ skb_set_hash(skb,
+ *(u32 *)extra->u.hash.value,
+ type);
+ }
+
XENVIF_TX_CB(skb)->pending_idx = pending_idx;
__skb_put(skb, data_len);
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-13 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1463128649-20832-1-git-send-email-paul.durrant@citrix.com>
2016-05-13 8:37 ` [PATCH net-next v4 1/4] xen-netback: add control ring boilerplate Paul Durrant
2016-05-13 8:37 ` [PATCH net-next v4 2/4] xen-netback: add control protocol implementation Paul Durrant
2016-05-13 8:37 ` [PATCH net-next v4 3/4] xen-netback: pass hash value to the frontend Paul Durrant
2016-05-13 8:37 ` Paul Durrant [this message]
[not found] ` <1463128649-20832-3-git-send-email-paul.durrant@citrix.com>
2016-05-13 11:20 ` [PATCH net-next v4 2/4] xen-netback: add control protocol implementation Wei Liu
2016-05-16 17:36 ` [PATCH net-next v4 0/4] xen-netback: support for control ring David Miller
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='1463128649-20832-5-git-send-email-paul.durrant__31096.1049901836$1463129573$gmane$org@citrix.com' \
--to=paul.durrant@citrix.com \
--cc=netdev@vger.kernel.org \
--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).