From: "Zhang, Helin" <helin.zhang@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Rowden, Aaron F" <aaron.f.rowden@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] i40e: workaround for X710 performance issues
Date: Tue, 16 Dec 2014 11:07:38 +0000 [thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A7D3BE6@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <2702920.KlIrzH6BZs@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Tuesday, December 16, 2014 4:37 PM
> To: Zhang, Helin
> Cc: dev@dpdk.org; Rowden, Aaron F; Chen, Jing D
> Subject: Re: [dpdk-dev] [PATCH v3] i40e: workaround for X710 performance
> issues
>
> Hi Helin,
>
> First, thank you and Jing for the excellent review process.
>
> 2014-12-16 16:23, Helin Zhang:
> > On X710, performance number is far from the expectation on recent
> > firmware versions. The fix for this issue may not be integrated in the
> > following firmware version. So the workaround in software driver is
> > needed. It needs to modify the initial values of 3 internal only
> > registers. Note that the workaround can be removed when it is fixed in
> > firmware in the future.
>
> I want to understand something here. You say the workaround can be removed
> when firmware will be fixed. But I suppose that some NICs won't be updated so
> the workaround will be needed forever?
Yes, it is possible. Let me check with our NIC marketing guys of their firmware update strategy before removing it.
Now it is quite useful for high performance. Thank you very much for pointing out this!
Regards,
Helin
>
> --
> Thomas
next prev parent reply other threads:[~2014-12-16 11:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 7:09 [dpdk-dev] [PATCH] " Helin Zhang
2014-12-15 7:56 ` [dpdk-dev] [PATCH v2] " Helin Zhang
2014-12-16 2:29 ` Chen, Jing D
2014-12-16 2:43 ` Zhang, Helin
2014-12-16 8:23 ` [dpdk-dev] [PATCH v3] " Helin Zhang
2014-12-16 8:37 ` Thomas Monjalon
2014-12-16 11:07 ` Zhang, Helin [this message]
2014-12-16 9:07 ` Chen, Jing D
2014-12-17 0:05 ` Thomas Monjalon
2015-01-08 2:43 ` Wu, Jingjing
2015-01-08 2:49 ` Zhang, Helin
2015-01-09 5:29 ` Wu, Jingjing
2015-01-09 15:48 ` Thomas Monjalon
2015-01-12 0:26 ` Zhang, Helin
2015-01-12 0:39 ` Wu, Jingjing
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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A7D3BE6@SHSMSX104.ccr.corp.intel.com \
--to=helin.zhang@intel.com \
--cc=aaron.f.rowden@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).