From: David Marchand <david.marchand@redhat.com>
To: "Edouard Gaulué" <listes@e-gaulue.com>
Cc: dev <dev@dpdk.org>, Beilei Xing <beilei.xing@intel.com>,
Jeff Guo <jia.guo@intel.com>, Qi Zhang <qi.z.zhang@intel.com>
Subject: Re: Difference between i40e and i40en?
Date: Wed, 4 May 2022 08:34:13 +0200 [thread overview]
Message-ID: <CAJFAV8z_=+MQN9O8hJgAg2RXjP1zo+gnmKbikXe3Hz65aE29kw@mail.gmail.com> (raw)
In-Reply-To: <20f0c2fc-b8bb-69c4-8e0a-9b2632893a4a@e-gaulue.com>
Hello Édouard,
On Tue, May 3, 2022 at 9:05 PM Edouard Gaulué <listes@e-gaulue.com> wrote:
>
> I just received a brand new server with an Intel X710 T4L inside. I
> hoped I could use it at 5GBaseT speed as claimed by Intel, but I couldn't.
>
> In fact, I run ESXi 6.7U3 on this new server and it looks it doesn't
> support this speed (2.5G neither). I downloaded Intel driver source code
> and discovered there was an incompatibility between 5GBaseT and DCB. But
> then vmware support team, point me the driver used by ESXi is i40en and
> not i40e.
>
> Are those drivers totally different? It looks to. Error strings found in
> vmkernel.log couldn't be found in the source code. Is there any way to
> get sources for i40en? For patching and rebuild.
>
> Any idea on who I should write to discuss with those i40en driver
> maintainers? Here or totally out of scope?
DPDK provides userspace drivers for various nics.
If you are looking at kernel drivers issues, then yes, your mail seems
out of scope :-).
Afaics, i40en is a VMware thing, so the solution is probably to
continue with VMware support.
I copied some Intel *DPDK* driver maintainers who might have a better idea.
--
David Marchand
next prev parent reply other threads:[~2022-05-04 6:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 13:17 Edouard Gaulué
2022-05-04 6:34 ` David Marchand [this message]
2022-05-04 9:09 ` Edouard Gaulué
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='CAJFAV8z_=+MQN9O8hJgAg2RXjP1zo+gnmKbikXe3Hz65aE29kw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jia.guo@intel.com \
--cc=listes@e-gaulue.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).