From: Akhil Goyal <akhil.goyal@nxp.com>
To: Adam Dybkowski <adamx.dybkowski@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"anatoly.burakov@intel.com" <anatoly.burakov@intel.com>
Cc: "fiona.trahe@intel.com" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH v5 1/1] doc: document vfio-pci usage with QAT PMD
Date: Wed, 28 Oct 2020 11:05:05 +0000 [thread overview]
Message-ID: <VI1PR04MB31682AF131AE8234FA5C058AE6170@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20201013141015.31232-2-adamx.dybkowski@intel.com>
> Subject: [PATCH v5 1/1] doc: document vfio-pci usage with QAT PMD
>
> This patch marks the old igb-uio driver as unsecure when used
> with the QAT PMD and updates all examples to recommend using
> vfio-pci instead.
> It also mentions security issues with the QAT CPM and provides
> information about the new vfio-pci parameter 'disable_denylist'
> available in Linux kernels 5.9 and later.
>
> Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2020-10-28 11:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 14:20 [dpdk-dev] [PATCH] " Adam Dybkowski
2020-09-08 16:00 ` Trahe, Fiona
2020-09-08 16:19 ` [dpdk-dev] [PATCH v2 0/1] " Adam Dybkowski
2020-09-08 16:19 ` [dpdk-dev] [PATCH v2 1/1] " Adam Dybkowski
2020-09-09 10:51 ` Burakov, Anatoly
2020-09-08 19:22 ` [dpdk-dev] [PATCH v2 0/1] " Mcnamara, John
2020-09-15 11:14 ` [dpdk-dev] [PATCH v3 " Adam Dybkowski
2020-09-15 11:14 ` [dpdk-dev] [PATCH v3 1/1] " Adam Dybkowski
2020-09-16 12:33 ` Burakov, Anatoly
2020-10-08 21:29 ` Akhil Goyal
2020-10-12 10:50 ` Dybkowski, AdamX
2020-10-12 10:43 ` [dpdk-dev] [PATCH v4 0/1] " Adam Dybkowski
2020-10-12 10:43 ` [dpdk-dev] [PATCH v4 1/1] " Adam Dybkowski
2020-10-13 14:10 ` [dpdk-dev] [PATCH v5 0/1] " Adam Dybkowski
2020-10-13 14:10 ` [dpdk-dev] [PATCH v5 1/1] " Adam Dybkowski
2020-10-28 11:05 ` Akhil Goyal [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=VI1PR04MB31682AF131AE8234FA5C058AE6170@VI1PR04MB3168.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=adamx.dybkowski@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@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).