From: Dmitry Fleytman <dmitry.fleytman@gmail.com>
To: Yuri Benditovich <yuri.benditovich@daynix.com>
Cc: Yan Vugenfirer <yan@daynix.com>, Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH 2/2] NetRxPkt: fix hash calculation of IPV6 TCP
Date: Wed, 29 Jan 2020 18:09:43 +0200 [thread overview]
Message-ID: <F97F4F13-3C10-4F39-A91F-B3341CD65CE6@gmail.com> (raw)
In-Reply-To: <20200127115405.13459-2-yuri.benditovich@daynix.com>
> On 27 Jan 2020, at 13:54, Yuri Benditovich <yuri.benditovich@daynix.com> wrote:
>
> When requested to calculate the hash for TCPV6 packet,
> ignore overrides of source and destination addresses
> in in extension headers.
> Use these overrides when new hash type NetPktRssIpV6TcpEx
> requested.
> Use this type in e1000e hash calculation for IPv6 TCP, which
> should take in account overrides of the addresses.
>
> Signed-off-by: Yuri Benditovich <yuri.benditovich@daynix.com>
Acked-by: Dmitry Fleytman <dmitry.fleytman@gmail.com>
> ---
> hw/net/e1000e_core.c | 2 +-
> hw/net/net_rx_pkt.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/net/e1000e_core.c b/hw/net/e1000e_core.c
> index 9b76f82db5..5b05c8ea8a 100644
> --- a/hw/net/e1000e_core.c
> +++ b/hw/net/e1000e_core.c
> @@ -582,7 +582,7 @@ e1000e_rss_calc_hash(E1000ECore *core,
> type = NetPktRssIpV4Tcp;
> break;
> case E1000_MRQ_RSS_TYPE_IPV6TCP:
> - type = NetPktRssIpV6Tcp;
> + type = NetPktRssIpV6TcpEx;
> break;
> case E1000_MRQ_RSS_TYPE_IPV6:
> type = NetPktRssIpV6;
> diff --git a/hw/net/net_rx_pkt.c b/hw/net/net_rx_pkt.c
> index b2a06bd27d..1e1c504e42 100644
> --- a/hw/net/net_rx_pkt.c
> +++ b/hw/net/net_rx_pkt.c
> @@ -348,7 +348,7 @@ net_rx_pkt_calc_rss_hash(struct NetRxPkt *pkt,
> assert(pkt->isip6);
> assert(pkt->istcp);
> trace_net_rx_pkt_rss_ip6_tcp();
> - _net_rx_rss_prepare_ip6(&rss_input[0], pkt, true, &rss_length);
> + _net_rx_rss_prepare_ip6(&rss_input[0], pkt, false, &rss_length);
> _net_rx_rss_prepare_tcp(&rss_input[0], pkt, &rss_length);
> break;
> case NetPktRssIpV6:
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-01-29 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 11:54 [PATCH 1/2] NetRxPkt: Introduce support for additional hash types Yuri Benditovich
2020-01-27 11:54 ` [PATCH 2/2] NetRxPkt: fix hash calculation of IPV6 TCP Yuri Benditovich
2020-01-29 16:09 ` Dmitry Fleytman [this message]
2020-01-29 16:09 ` [PATCH 1/2] NetRxPkt: Introduce support for additional hash types Dmitry Fleytman
2020-02-12 8:50 ` Yuri Benditovich
2020-02-12 9:01 ` Jason Wang
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=F97F4F13-3C10-4F39-A91F-B3341CD65CE6@gmail.com \
--to=dmitry.fleytman@gmail.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yan@daynix.com \
--cc=yuri.benditovich@daynix.com \
/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).