From: "Li, Xiaoyun" <xiaoyun.li@intel.com>
To: Yuanhan Liu <yliu@fridaylinux.org>
Cc: "Yang, Qiming" <qiming.yang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>, Matt Laswell <laswell@infinite.io>
Subject: Re: [dpdk-dev] Occasional instability in RSS Hashes/Queues from X540 NIC
Date: Wed, 19 Jul 2017 06:17:23 +0000 [thread overview]
Message-ID: <B9E724F4CB7543449049E7AE7669D82F428F2F@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20170718140101.GS11626@yliu-home>
Hi, Yuanhan !
I did the same tests on DPDK 16.11 this morning and cannot reproduce the problem on 16.11. It seems that the problem has been fixed on version 16.11.
So could you reproduce the problem on 16.11 LTS release? I think maybe it has been fixed already.
Best regards
Xiaoyun Li
-----Original Message-----
From: Yuanhan Liu [mailto:yliu@fridaylinux.org]
Sent: Tuesday, July 18, 2017 22:01
To: Matt Laswell <laswell@infinite.io>
Cc: Yang, Qiming <qiming.yang@intel.com>; dev@dpdk.org; Li, Xiaoyun <xiaoyun.li@intel.com>
Subject: Re: [dpdk-dev] Occasional instability in RSS Hashes/Queues from X540 NIC
On Tue, Jul 18, 2017 at 08:43:42AM -0500, Matt Laswell wrote:
> Hi Qiming,
>
> That's fantastic news. Thank you very much for taking the time to
> figure the issue out.
>
> Would it be possible to backport the fix to the 16.11 LTS release? This
> kind of problem seems tailor-made for LTS.
Agreed. You might want to find the fix commit with git bisect.
--yliu
next prev parent reply other threads:[~2017-07-19 6:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 13:04 Matt Laswell
2017-05-04 16:34 ` Wiles, Keith
2017-05-04 18:15 ` Matt Laswell
2017-05-05 13:05 ` Matt Laswell
2017-05-08 8:55 ` Yang, Qiming
2017-07-18 8:58 ` Yang, Qiming
2017-07-18 13:43 ` Matt Laswell
2017-07-18 14:01 ` Yuanhan Liu
2017-07-19 6:17 ` Li, Xiaoyun [this message]
2017-07-19 8:13 ` Li, Xiaoyun
2017-07-19 10:54 ` Yuanhan Liu
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=B9E724F4CB7543449049E7AE7669D82F428F2F@SHSMSX101.ccr.corp.intel.com \
--to=xiaoyun.li@intel.com \
--cc=dev@dpdk.org \
--cc=laswell@infinite.io \
--cc=qiming.yang@intel.com \
--cc=yliu@fridaylinux.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).