From: Yuanhan Liu <yliu@fridaylinux.org>
To: Matt Laswell <laswell@infinite.io>
Cc: "Yang, Qiming" <qiming.yang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Li, Xiaoyun" <xiaoyun.li@intel.com>
Subject: Re: [dpdk-dev] Occasional instability in RSS Hashes/Queues from X540 NIC
Date: Tue, 18 Jul 2017 22:01:01 +0800 [thread overview]
Message-ID: <20170718140101.GS11626@yliu-home> (raw)
In-Reply-To: <CA+GnqArnV-LR3dKd=KZ4zLqUb93=ZEVTZ4hNwtGYEO=ngU2fxQ@mail.gmail.com>
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-18 14:01 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 [this message]
2017-07-19 6:17 ` Li, Xiaoyun
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=20170718140101.GS11626@yliu-home \
--to=yliu@fridaylinux.org \
--cc=dev@dpdk.org \
--cc=laswell@infinite.io \
--cc=qiming.yang@intel.com \
--cc=xiaoyun.li@intel.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).