From: Peter Morrow <peter@graphiant.com>
To: "users@dpdk.org" <users@dpdk.org>
Cc: "simei.su@intel.com" <simei.su@intel.com>
Subject: Intel e1000 driver + i350 with copper SFP modules
Date: Tue, 28 May 2024 14:26:58 +0000 [thread overview]
Message-ID: <PH0PR17MB46394E3936936868273FCC73BDF12@PH0PR17MB4639.namprd17.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1584 bytes --]
Hello,
I have an Intel i350 NIC which is using the e1000 dpdk driver (dpdk version 22.11.4), I also have a copper SFP module (Finisar PNFCLF8522P2BTL) which I was hoping to use with this NIC. During testing the NIC/SFP combination seems to work fine as the link comes up fine after boot and passes traffic whilst using VPP with DPDK, however if the SFP is removed and re-inserted the link will never come back up.
Reading the source code for the e1000 driver I came across:
https://github.com/DPDK/dpdk/blob/main/drivers/net/e1000/igb_ethdev.c#L5100
Which seems to indicate that there isn't complete support for copper media SFP modules with the driver and/or NIC, I am thinking this explains why things like hot plug don't appear to work. I took DPDK out of the picture and see the same behaviour with Linux 6.1.0-21-amd64, which further makes me believe there is an incompatibility here with my chosen (or in fact all) copper SFP modules. Would anyone more knowledgeable with this driver be able to shed some light on what I am seeing here?
The device details are as follows:
gnos@cpe:~$ sudo lshw -c network -businfo
Bus info Device Class Description
=======================================================
pci@0000:02:00.0<mailto:pci@0000:02:00.0> network I350 Gigabit Fiber Network Connection
pci@0000:02:00.1<mailto:pci@0000:02:00.1> network I350 Gigabit Fiber Network Connection
The PCI device id is 8086:1522
Any help or pointers you can give are much appreciated!
Thank you,
Peter.
[-- Attachment #2: Type: text/html, Size: 7933 bytes --]
next reply other threads:[~2024-06-10 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 14:26 Peter Morrow [this message]
2024-05-31 9:50 Peter Morrow
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=PH0PR17MB46394E3936936868273FCC73BDF12@PH0PR17MB4639.namprd17.prod.outlook.com \
--to=peter@graphiant.com \
--cc=simei.su@intel.com \
--cc=users@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).