All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Michał Krawczyk" <mk@semihalf.com>
Cc: Amiya Mohakud <amohakud@paloaltonetworks.com>, dev <dev@dpdk.org>,
	Sachin Kanoje <skanoje@paloaltonetworks.com>,
	Megha Punjani <mpunjani@paloaltonetworks.com>,
	Sharad Saha <ssaha@paloaltonetworks.com>,
	Eswar Sadaram <esadaram@paloaltonetworks.com>,
	"Brandes, Shai" <shaibran@amazon.com>,
	ena-dev <ena-dev@semihalf.com>
Subject: Re: DPDK:20.11.1: net/ena crash while fetching xstats
Date: Tue, 19 Apr 2022 16:09:42 -0700	[thread overview]
Message-ID: <20220419160942.75fd8703@hermes.local> (raw)
In-Reply-To: <CAJMMOfPpvuBPJT2BihhSQSt9Rwx5cFphpKmfRAN71QJ6VMAxrw@mail.gmail.com>

On Tue, 19 Apr 2022 22:27:32 +0200
Michał Krawczyk <mk@semihalf.com> wrote:

> Thanks Stephen, indeed the issue reproduces in the secondary process.
> 
> Basically ENA v2.2.1 is not MP aware, meaning it cannot be used safely
> from the secondary process. The main obstacle is the admin queue which
> is used for processing the hardware requests which can be used safely
> only from the primary process. It's not strictly a bug, as we weren't
> exposing 'MP Awareness' in the PMD features list, it's more like a
> lack of proper MP support.
> 
> The latest ENA PMD release should be MP safe. We currently don't have
> PMD backport ready for the older LTS release (but we're planning to do
> so for ENA v2.6.0 on the amzn-drivers repository:
> https://github.com/amzn/amzn-drivers/tree/master/userspace/dpdk). 

I wish that ENA did not have its own versioning scheme.
Driver versions are meaningful only to the driver writer/vendor, they
don't help the end user.

Since backporting is not part of stable process. I suggest doing what
XDP did for 21.11 and earlier releases.

diff --git a/drivers/net/ena/ena_ethdev.c b/drivers/net/ena/ena_ethdev.c
index 634c97acf60d..3778349f3fe9 100644
--- a/drivers/net/ena/ena_ethdev.c
+++ b/drivers/net/ena/ena_ethdev.c
@@ -3212,6 +3212,12 @@ static int ena_rx_queue_intr_disable(struct rte_eth_dev *dev,
 static int eth_ena_pci_probe(struct rte_pci_driver *pci_drv __rte_unused,
        struct rte_pci_device *pci_dev)
 {
+       if (rte_eal_process_type() == RTE_PROC_SECONDARY) {
+               PMD_INIT_LOG(ERR,
+                           "Ena PMD does not support secondary processes\n");
+               return -ENOTSUP;
+       }
+
        return rte_eth_dev_pci_generic_probe(pci_dev,
                sizeof(struct ena_adapter), eth_ena_dev_init);
 }

  parent reply	other threads:[~2022-04-19 23:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18  8:33 DPDK:20.11.1: net/ena crash while fetching xstats Amiya Mohakud
2022-04-18 15:18 ` Amiya Mohakud
2022-04-19 12:10   ` Michał Krawczyk
2022-04-19 15:01     ` Stephen Hemminger
2022-04-19 20:27       ` Michał Krawczyk
2022-04-19 22:25         ` Stephen Hemminger
2022-04-19 23:09         ` Stephen Hemminger [this message]
2022-04-20  8:37           ` Amiya Mohakud

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=20220419160942.75fd8703@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=amohakud@paloaltonetworks.com \
    --cc=dev@dpdk.org \
    --cc=ena-dev@semihalf.com \
    --cc=esadaram@paloaltonetworks.com \
    --cc=mk@semihalf.com \
    --cc=mpunjani@paloaltonetworks.com \
    --cc=shaibran@amazon.com \
    --cc=skanoje@paloaltonetworks.com \
    --cc=ssaha@paloaltonetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.