From: Roman Khromenok <roma55592@yandex.ru>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH 0/3] net/intel: make link state configurable on device start
Date: Fri, 2 Oct 2026 21:43:35 +0200 [thread overview]
Message-ID: <cover.1790970122.git.roma55592@yandex.ru> (raw)
Starting a port always brings its link up, so the link partner sees
the port as soon as the application starts it. An application that
enables ports only after its own configuration is applied, such as
a firewall or a switch, cannot keep a disabled port dark: it can only
bring the link down right after rte_eth_dev_start(), and the link
partner may still see the link flap.
The ice driver already has the link_state_on_close device argument to
choose the link state when the port is stopped. This series adds its
counterpart, link_state_on_start, to the ice, i40e and ixgbe drivers:
-a <pci>,link_state_on_start=down
With "down", the port is started with the link down, and the
application brings it up later with rte_eth_dev_set_link_up().
The default "up" keeps the current behavior.
ixgbe has no firmware command to bring the link down, so "down" leaves
the port in the same state as rte_eth_dev_set_link_down(): the laser
is kept off on fiber links, the copper PHY is powered off right after
the link setup.
Tested with testpmd on E810-C (ice, firmware 4.60) connected to
a network packet broker: with link_state_on_start=down the link stays
down after the port start and the link partner does not see it until
"set link-up"; without the device argument the link comes up on start
as before. i40e and ixgbe are build tested only.
Roman Khromenok (3):
net/ice: make link state configurable on device start
net/i40e: make link state configurable on device start
net/ixgbe: make link state configurable on device start
doc/guides/nics/i40e.rst | 13 ++++++
doc/guides/nics/ice.rst | 13 ++++++
doc/guides/nics/ixgbe.rst | 13 ++++++
doc/guides/rel_notes/release_26_11.rst | 13 +++++-
drivers/net/intel/i40e/i40e_ethdev.c | 58 +++++++++++++++++++++++++-
drivers/net/intel/i40e/i40e_ethdev.h | 2 +
drivers/net/intel/ice/ice_ethdev.c | 36 +++++++++++++++-
drivers/net/intel/ice/ice_ethdev.h | 1 +
drivers/net/intel/ixgbe/ixgbe_ethdev.c | 44 ++++++++++++++++++-
drivers/net/intel/ixgbe/ixgbe_ethdev.h | 2 +
10 files changed, 187 insertions(+), 8 deletions(-)
--
2.47.3
next reply other threads:[~2026-10-02 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 19:43 Roman Khromenok [this message]
2026-10-02 19:43 ` [PATCH 1/3] net/ice: make link state configurable on device start Roman Khromenok
2026-10-02 19:43 ` [PATCH 2/3] net/i40e: " Roman Khromenok
2026-10-02 19:43 ` [PATCH 3/3] net/ixgbe: " Roman Khromenok
2026-10-03 16:18 ` [PATCH 0/3] net/intel: " Stephen Hemminger
2026-10-03 21:53 ` Roman Khromenok
2026-10-04 16:15 ` Stephen Hemminger
2026-10-04 16:13 ` Stephen Hemminger
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=cover.1790970122.git.roma55592@yandex.ru \
--to=roma55592@yandex.ru \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=vladimir.medvedkin@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