DPDK patches and discussions
 help / color / mirror / Atom feed
From: Abdelfattah Chehab <abdelfattah.chehab-ext@ekinops.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [DPDK 20.11] ixgbe VF PMD does not support LSC interrupts.
Date: Fri, 3 Jun 2022 14:44:55 +0000	[thread overview]
Message-ID: <PR1P264MB2030F648796CE26AE3826F72DFA19@PR1P264MB2030.FRAP264.PROD.OUTLOOK.COM> (raw)

[-- Attachment #1: Type: text/plain, Size: 815 bytes --]

Hi All,
While using net_e1000_igb_vf PMD, registering LSC Callbacks will have no effect.
rte_eth_dev_callback_register(port, RTE_ETH_EVENT_INTR_LSC, callback, NULL);

in the PMD code:
 .drv_flags = RTE_PCI_DRV_NEED_MAPPING

While for other working PMDs:
drv_flags = RTE_PCI_DRV_NEED_MAPPING | RTE_PCI_DRV_INTR_LSC

Meanwhile, The link status is updated correctly on demand:
(gdb) call rte_eth_link_get(4, $mylink)
$3 = 0
(gdb) p *$mylink
$4 = {link_speed = 1000, link_duplex = 1, link_autoneg = 1, link_status = 1}
(gdb) call rte_eth_link_get(4, $mylink)
$5 = 0
(gdb) p *$mylink
$6 = {link_speed = 0, link_duplex = 0, link_autoneg = 0, link_status = 0}

Does it mean that I have to fetch the link using poll action?
Will LSC interrupt be implemented for this PMD in future release ?

Thanks

[-- Attachment #2: Type: text/html, Size: 4049 bytes --]

                 reply	other threads:[~2022-06-05  7:52 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=PR1P264MB2030F648796CE26AE3826F72DFA19@PR1P264MB2030.FRAP264.PROD.OUTLOOK.COM \
    --to=abdelfattah.chehab-ext@ekinops.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).