From: Jerin Jacob <jerinjacobk@gmail.com>
To: Krzysztof Kanas <kkanas@marvell.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-dev <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>,
Maciej Czekaj <mczekaj@marvell.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: thunderx: explain which PCI is secondary VF
Date: Mon, 3 Feb 2020 13:36:41 +0530 [thread overview]
Message-ID: <CALBAE1Mcsk5vH0i2x8GzJ4m3v9dKqd9Yxb+-EnqZs2KOQY9fUg@mail.gmail.com> (raw)
In-Reply-To: <20200128133147.16500-1-kkanas@marvell.com>
On Tue, Jan 28, 2020 at 7:01 PM <kkanas@marvell.com> wrote:
>
> From: Krzysztof Kanas <kkanas@marvell.com>
>
> Thunderx-nic uses secondary VF's to provide more queues to DPDK.
> Current instructions explain the concept but don't show easy way to find
> which PCI id is primary and which is secondary VF's.
>
> Signed-off-by: Krzysztof Kanas <kkanas@marvell.com>
> ---
> doc/guides/nics/thunderx.rst | 48 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 48 insertions(+)
1) Fixed the following warning
- dpdk-next-net-mrvl/doc/guides/nics/thunderx.rst:321: WARNING:
Explicit markup ends without a blank line; unexpected unindent.
2) Slightly reworded the git commit message.
doc/thunderx: add secondary VF enumeration details
thunderx-nic uses secondary VF's to provide more queues to DPDK.
Current instructions explain the concept but don't show an easy way to find
which PCI id is primary and which is secondary VF's.
This patch extending the documentation of secondary VF w.r.t
the enumeration details.
Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied to dpdk-next-net-mrvl/master. Thanks
prev parent reply other threads:[~2020-02-03 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 13:31 kkanas
2020-02-03 8:06 ` Jerin Jacob [this message]
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=CALBAE1Mcsk5vH0i2x8GzJ4m3v9dKqd9Yxb+-EnqZs2KOQY9fUg@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=kkanas@marvell.com \
--cc=marko.kovacevic@intel.com \
--cc=mczekaj@marvell.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).