From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Qi Zhang <qi.z.zhang@intel.com>,
john.mcnamara@intel.com, jingjing.wu@intel.com
Cc: helin.zhang@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] doc: add known issue for i40e VF performance
Date: Mon, 3 Jul 2017 11:26:30 +0100 [thread overview]
Message-ID: <20f400c0-c1c0-acba-6c89-0ae478faa8d4@intel.com> (raw)
In-Reply-To: <20170703035754.4622-1-qi.z.zhang@intel.com>
On 7/3/2017 4:57 AM, Qi Zhang wrote:
> VF performance is limited by the kernel PCI extended tag setting.
> Update the document to explain the known issue and the workaround.
>
> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
Hi Qi, John,
Not related to the content, but related to location, where a "known
issue" should go, release notes or component specific document?
Thanks,
ferruh
next prev parent reply other threads:[~2017-07-03 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 3:57 Qi Zhang
2017-07-03 10:01 ` Mcnamara, John
2017-07-03 10:26 ` Ferruh Yigit [this message]
2017-07-09 22:49 ` Thomas Monjalon
2017-07-18 9:52 ` [dpdk-dev] [PATCH v3] " Qi Zhang
2017-07-18 14:59 ` Ferruh Yigit
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=20f400c0-c1c0-acba-6c89-0ae478faa8d4@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=jingjing.wu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=qi.z.zhang@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).