From: David Marchand <david.marchand@redhat.com>
To: "Peng, Yuan" <yuan.peng@intel.com>
Cc: "Jiang, YuX" <yux.jiang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [PATCH V2] doc: add ice in-tree driver version for Intel NICs
Date: Tue, 25 Oct 2022 10:23:07 +0200 [thread overview]
Message-ID: <CAJFAV8w+890DAQnufSb+55f2_iQwAceoYLVcka-zAAtUtEKyfg@mail.gmail.com> (raw)
In-Reply-To: <SA2PR11MB5068518F9E3CB1BAF74362DCFE319@SA2PR11MB5068.namprd11.prod.outlook.com>
On Tue, Oct 25, 2022 at 4:52 AM Peng, Yuan <yuan.peng@intel.com> wrote:
>
> Hi Marchand,
>
> Tested platform in this document lists all the platforms including CPU, OS and NIC type with SW package version.
> We submitted the patch to add our actual tested ice in-tree driver version of E810 NIC in this DPDK release.
> I think it should be added here.
Ok, you can put the information here, as it was before.
But I am asking for more, see below.
> doc/guides/nics/ice.rst is a document for ICE driver introduction.
- Sorry, I meant iavf.rst.
The dependency on ice PF driver wrt features availability of the iavf
driver must be documented.
We had reports for couple of issues.
Those issues were hard to understand due to really poor (read: absent)
documentation.
After investigating (having to play with differents versions of
kernel, dpdk, firmwares, oot driver ...), we realise it is due to poor
decisions from Intel on implementing features in the ice OOT driver
only.
Because of this, DPDK developers are locked with this OOT driver
instead of relying on the upstream kernel.
This is a bad thing for both DPDK and kernel communities.
- This current patch only shows focus for tests against two
distributions, with a fixed release version.
I insist that Intel QE must validate the iavf dpdk drivers against the
*upstream* ice kernel driver.
--
David Marchand
prev parent reply other threads:[~2022-10-25 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 7:12 Yu Jiang
2022-10-19 1:51 ` Lin, Xueqin
2022-10-19 8:46 ` David Marchand
2022-10-25 2:52 ` Peng, Yuan
2022-10-25 8:23 ` David Marchand [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=CAJFAV8w+890DAQnufSb+55f2_iQwAceoYLVcka-zAAtUtEKyfg@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=qi.z.zhang@intel.com \
--cc=yuan.peng@intel.com \
--cc=yux.jiang@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).