DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tom Rix <trix@redhat.com>
To: Nicolas Chautru <nicolas.chautru@intel.com>,
	dev@dpdk.org, akhil.goyal@nxp.com, thomas@monjalon.net
Cc: john.mcnamara@intel.com, david.marchand@redhat.com,
	bruce.richardson@intel.com, tianjiao.liu@intel.com
Subject: Re: [dpdk-dev] [PATCH v3] doc: add reference to bbdev companion configuration tool
Date: Tue, 3 Nov 2020 11:59:49 -0800	[thread overview]
Message-ID: <cd903316-1332-7ebe-6c41-5d62f451edbe@redhat.com> (raw)
In-Reply-To: <1604432376-28515-1-git-send-email-nicolas.chautru@intel.com>

On 11/3/20 11:39 AM, Nicolas Chautru wrote:
> v3: casing typo correction
> v2: typo corrections
> Adding reference to companion tool to perform PF device configuration of HW bbdev devices : pf_bb_config This topic was previously discussed in https://patches.dpdk.org/patch/74270/
> and it was preferred for the tool to be be upstreamed outside of DPDK in github.
> This dependency notably allows to run the bbdev workload from VF.
> Kept this as a single commit affecting the 3 distinct docs.
> Nicolas Chautru (1):
>   doc: add reference to companion configuration tool
>  doc/guides/bbdevs/acc100.rst        | 19 +++++++++++++++++++
>  doc/guides/bbdevs/fpga_5gnr_fec.rst | 19 +++++++++++++++++++
>  doc/guides/bbdevs/fpga_lte_fec.rst  | 19 +++++++++++++++++++
>  3 files changed, 57 insertions(+)
Looks good, thanks.

Reviewed-by: Tom Rix <trix@redhat.com>

  parent reply	other threads:[~2020-11-03 20:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03 19:39 Nicolas Chautru
2020-11-03 19:39 ` [dpdk-dev] [PATCH v3] doc: add reference to " Nicolas Chautru
2020-11-03 19:59 ` Tom Rix [this message]
2020-11-09 19:24   ` [dpdk-dev] [PATCH v3] doc: add reference to bbdev " Chautru, Nicolas
2020-11-12 21:02     ` Akhil Goyal
2020-11-12 22:27       ` Chautru, Nicolas

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cd903316-1332-7ebe-6c41-5d62f451edbe@redhat.com \
    --to=trix@redhat.com \
    --cc=akhil.goyal@nxp.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=nicolas.chautru@intel.com \
    --cc=thomas@monjalon.net \
    --cc=tianjiao.liu@intel.com \


* 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).