From: "Edouard Gaulué" <listes@e-gaulue.com>
To: <dev@dpdk.org>
Subject: Difference between i40e and i40en?
Date: Tue, 3 May 2022 15:17:54 +0200 [thread overview]
Message-ID: <20f0c2fc-b8bb-69c4-8e0a-9b2632893a4a@e-gaulue.com> (raw)
Hi community,
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?
Regards, Édouard
next reply other threads:[~2022-05-03 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 13:17 Edouard Gaulué [this message]
2022-05-04 6:34 ` David Marchand
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=20f0c2fc-b8bb-69c4-8e0a-9b2632893a4a@e-gaulue.com \
--to=listes@e-gaulue.com \
--cc=dev@dpdk.org \
/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).