DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ming 1. Yang (NSB)" <ming.1.yang@nokia-sbell.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "Anatoly Burakov" <anatoly.burakov@intel.com>,
	"Bruce Richardson" <bruce.richardson@intel.com>,
	"Kevin Laatz" <kevin.laatz@intel.com>,
	"Morten Brørup" <mb@smartsharesystems.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [External] Re: [PATCH] eal: fix bus cleanup in secondary process
Date: Tue, 3 Dec 2024 09:23:02 +0000	[thread overview]
Message-ID: <VI1PR07MB9898C052A454F92A6F512F11A3362@VI1PR07MB9898.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <20241128091552.2406f1a3@hermes.local>

Hi Stephen,

Yes, You're right. I'm making a new patch for improving in crypto device to solve this issue. And the modification has already worked in our cases.
Anyway, I will upload the patch soon and will mark the status of this patch to Superseded. Thanks.

Brs,
Yang Ming

-----Original Message-----
From: Stephen Hemminger <stephen@networkplumber.org> 
Sent: 2024年11月29日 1:16
To: Ming 1. Yang (NSB) <ming.1.yang@nokia-sbell.com>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>; Bruce Richardson <bruce.richardson@intel.com>; Kevin Laatz <kevin.laatz@intel.com>; Morten Brørup <mb@smartsharesystems.com>; dev@dpdk.org; stable@dpdk.org
Subject: [External] Re: [PATCH] eal: fix bus cleanup in secondary process

Caution: This is an external email. Please be very careful when clicking links or opening attachments. See http://nok.it/nsb for additional information.

On Thu, 28 Nov 2024 13:48:29 +0800
myang <ming.1.yang@nokia-sbell.com> wrote:

> eal_bus_cleanup has been added in rte_eal_cleanup. But for secondary 
> process, eal_bus_cleanup will trigger vdev_cleanup which trigger 
> rte_vdev_driver to remove. Then our crypto devices will execute 
> ipsec_mb_remove to rte_cryptodev_pmd_destroy.
> 
> Finally error logs occur as below:
> CRYPTODEV: rte_cryptodev_close() line 1453: Device 0 must be stopped 
> before closing
> EAL: failed to send to (/tmp/dpdk/l2hicu/mp_socket) due to Bad file 
> descriptor
> EAL: Fail to send request /tmp/dpdk/l2hicu/mp_socket:ipsec_mb_mp_msg
> USER1: Create MR request to primary process failed.
> 
> Function call trace: rte_eal_cleanup->eal_bus_cleanup->
> vdev_cleanup->rte_vdev_driver->ipsec_mb_remove->
> 1. ipsec_mb_remove->rte_cryptodev_pmd_destroy->
> rte_cryptodev_pmd_release_device->rte_cryptodev_close
> 2. ipsec_mb_remove->ipsec_mb_qp_release->ipsec_mb_secondary_qp_op
> ->rte_mp_request_async->mp_request_async
> 
> Fixes: 1cab1a40ea9b ("bus: cleanup devices on shutdown")
> Cc: stable@dpdk.org
> 
> Signed-off-by: myang <ming.1.yang@nokia-sbell.com>

There is was a reason for calling cleanup on shutdown.
It looks like more of a bug in the crypto device not the EAL.


Freebsd and Windows also calls eal_bus_cleanup.




  reply	other threads:[~2024-12-03  9:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-28  5:48 myang
2024-11-28 17:15 ` Stephen Hemminger
2024-12-03  9:23   ` Ming 1. Yang (NSB) [this message]
2025-01-03  3:09 ` [PATCH v2] cryptodev: not close device when secondary exit Yang Ming

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=VI1PR07MB9898C052A454F92A6F512F11A3362@VI1PR07MB9898.eurprd07.prod.outlook.com \
    --to=ming.1.yang@nokia-sbell.com \
    --cc=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=kevin.laatz@intel.com \
    --cc=mb@smartsharesystems.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.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).