From: Dmitry Vyal <dmitryvyal@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] SFP/SFP+ modules hotplugging question.
Date: Mon, 11 Aug 2014 16:01:15 +0400 [thread overview]
Message-ID: <53E8B08B.5000406@gmail.com> (raw)
Dear mailing list, I have a question concerning SFP modules hotplugging.
I made some experiments and want to confirm my findings.
Looks like hotplug is basically supported out of the box, the only thing
one has to do is to register
callbacks for RTE_ETH_EVENT_INTR_LSC and avoid sending mbufs to NIC when
link is down.
Implemented that, I can now remove an SFP module in the middle on a run
and insert another one and NIC operation resumes.
So far so good. But then I inserted an SFP module into SFP+ slot during
the testing I got an unsatisfactory behavior.
Link went down but to my surprise it didn't go up after I replaced SFP
module with one of SFP+ type.
I had to restart the application to bring port back into the working state.
So my question is whether it's possible to detect and gracefully
overcome such situations without disrupting other ports operation?
P.S. Forgot to mention, I observed this behavior with DPDK-1.5.1 and
82599EB NIC.
Best regards,
Dmitry.
reply other threads:[~2014-08-11 11:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53E8B08B.5000406@gmail.com \
--to=dmitryvyal@gmail.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).