DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Qi Zhang <qi.z.zhang@intel.com>
Cc: dev@dpdk.org, john.mcnamara@intel.com, jingjing.wu@intel.com,
	helin.zhang@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] doc: add known issue for i40e VF performance
Date: Mon, 10 Jul 2017 00:49:46 +0200	[thread overview]
Message-ID: <5809031.eT3YHgoUoZ@xps> (raw)
In-Reply-To: <20170703035754.4622-1-qi.z.zhang@intel.com>

Hi,

Few typos spotted

03/07/2017 05:57, Qi Zhang:
> --- a/doc/guides/nics/i40e.rst
> +++ b/doc/guides/nics/i40e.rst
> @@ -447,3 +447,30 @@ It means if APP has set the max bandwidth for that TC, it comes to no
>  effect.
>  It's suggested to set the strict priority mode for a TC that is latency
>  sensitive but no consuming much bandwidth.
> +
> +VF performance is impacted by PCI extended tag setting
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +To reach maximum NIC performance in the VF the PCI extended tag must be
> +enabled. The DPDK I40E PF drvier will set this feature during initialization,

drvier -> driver

> +but the kernel PF driver does not. So when running traffic on a VF which is
> +managed by the kernel PF driver, a significent NIC performance downgrade has

significent -> significant

> +been observed (for 64 byte packets, there is about 25% linerate downgrade for
> +a 25G device and about 35% for a 40G device).
> +
> +For kernel version >= 4.11, the kernel's PCI driver will enable the extended
> +tag if it detects that the device supports it. So by default, this is not an
> +issue. For kernels <= 4.11 or When the PCI extended tag is disabled it can be

When -> when

> +enabled using the steps below.
> +
> +#. Get the current value of the PCI configure register::
> +
> +      setpci -s <XX:XX.X> a8.w
> +
> +#. Set bit 8::
> +
> +      value = value | 0x100
> +
> +#. Set the PCI configure register with new value::
> +
> +      setpci -s <XX:XX.X> a8.w=<value>

  parent reply	other threads:[~2017-07-09 22:49 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
2017-07-09 22:49 ` Thomas Monjalon [this message]
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=5809031.eT3YHgoUoZ@xps \
    --to=thomas@monjalon.net \
    --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).