DPDK usage discussions
 help / color / mirror / Atom feed
From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: Matan Azrad <matan@nvidia.com>, jinag <15720603159@163.com>,
	"users@dpdk.org" <users@dpdk.org>,
	Shahaf Shuler <shahafs@nvidia.com>
Subject: RE: Does the mlx5 NIC support reloading
Date: Thu, 17 Aug 2023 05:13:18 +0000	[thread overview]
Message-ID: <DM6PR12MB37530FA6F9B22EC3ABDB2F8BDF1AA@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <DM4PR12MB538998AA9976F002F4AFA48FDF17A@DM4PR12MB5389.namprd12.prod.outlook.com>

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

Hi, Jinag

5 cents to add: please see how FailSafe PMD handles device removal events and probes the devices periodically.
This is good example to understand how device hotplug works (Failsafe uses rte_eal_hotplug_add())
Also,  to add the device the previous instance should closed (RTE_ETH_EVENT_INTR_RMV) shoud be handled accordingly.

With best regards,

From: Matan Azrad <matan@nvidia.com>
Sent: Monday, August 14, 2023 9:41 AM
To: jinag <15720603159@163.com>; users@dpdk.org; Shahaf Shuler <shahafs@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: RE: Does the mlx5 NIC support reloading

Hi Jinag

After plugging out the device from the bus, you need to get the event RTE_ETH_EVENT_INTR_RMV.
You need to listen to this event and close the port when you see it.

After plugging in the device, you need to scan the bus again and attach the mlx5 device, so it will be probed again and a new ethdev port will be created.

Then, you need to reconfigure the port, as regular, and reuse the device.


From: jinag <15720603159@163.com<mailto:15720603159@163.com>>
Sent: Monday, 14 August 2023 6:07
To: users@dpdk.org<mailto:users@dpdk.org>; Matan Azrad <matan@nvidia.com<mailto:matan@nvidia.com>>; Shahaf Shuler <shahafs@nvidia.com<mailto:shahafs@nvidia.com>>; Slava Ovsiienko <viacheslavo@nvidia.com<mailto:viacheslavo@nvidia.com>>
Subject: Does the mlx5 NIC support reloading

External email: Use caution opening links or attachments

I am verifying the reload function of the mlx5 nic based on dpdk 19.11:
echo 1 > /sys/bus/pci/devices/$pci_address/remove
echo 1 > /sys/bus/pci/rescan
    net_mlx5: port 0 TX queue 0 CQ creation failure
    net_mlx5: port 0 TX queue allocation failed: cannot allocate memory
The nic cannot be reinitialized.

I am not sure if the above operation is correct. Could you please tell me if the mlx5 nic supports reloading(for example, the network card is down during normal  operation) and which dpdk functions need to be called.


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

  parent reply	other threads:[~2023-08-17  5:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14  3:06 jinag
2023-08-14  6:41 ` Matan Azrad
2023-08-14 10:05   ` jinag
2023-08-14 10:25     ` Matan Azrad
2023-08-17  5:13   ` Slava Ovsiienko [this message]
2023-08-24  7:35     ` jinag
  -- strict thread matches above, loose matches on Subject: below --
2023-08-14  2:58 jinag

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM6PR12MB37530FA6F9B22EC3ABDB2F8BDF1AA@DM6PR12MB3753.namprd12.prod.outlook.com \
    --to=viacheslavo@nvidia.com \
    --cc=15720603159@163.com \
    --cc=matan@nvidia.com \
    --cc=shahafs@nvidia.com \
    --cc=users@dpdk.org \


* 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).