From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by dpdk.org (Postfix, from userid 33) id A33BE1B13B; Fri, 28 Sep 2018 11:35:23 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Fri, 28 Sep 2018 09:35:23 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: cryptodev X-Bugzilla-Version: 17.05 X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: wenjing.1.jin@nokia-sbell.com X-Bugzilla-Status: CONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 93] crypto vdev create will reset the dev_started flag when one dpdk process has been up the crypto vdev X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2018 09:35:23 -0000 https://bugs.dpdk.org/show_bug.cgi?id=3D93 Bug ID: 93 Summary: crypto vdev create will reset the dev_started flag when one dpdk process has been up the crypto vdev Product: DPDK Version: 17.05 Hardware: All OS: All Status: CONFIRMED Severity: major Priority: Normal Component: cryptodev Assignee: dev@dpdk.org Reporter: wenjing.1.jin@nokia-sbell.com Target Milestone: --- when use crypto vdev in one group primary/secondary processes, when one pro= cess up the crypto vdev , if anther dpdk process startup with same dpdk crypto v= dev paramters, that will lead to the up vdev started flag set to 0. from the code, if we want to use the vdev in secondary process , it must be create in primary dpdk process first,and the secondary process which want u= se the crypto vdev need startup with same dpdk vdev parameters(--vdev).but when one dpdk process start after the crypto vdev up in one process , the vdev started flag will reset to 0. this seem not an expected result,this will br= oke the active cryptodev using. test step: 1: create one crypto vdev in primary dpdk process and then configu= red and start the crypto vdev .=20 2: startup secondary dpdk process with same crypto vdev parameters(crypto vdev will create in rte_eal_init()) expected result: crypto vdev stats normal in first process=20=20 actual result: crypto vdev dev_started set to 0 same issue with up crypto vdev in one secondary process and startup other secondary process with same crypto parameters this issue will result in different dpdk process can configured and start crypto vdev independently in such scenario, it seem not an expected result.= =20 from the code we can see=20 rte_cryptodev_pmd_allocate { .............. if (cryptodev->data =3D=3D NULL) { struct rte_cryptodev_data *cryptodev_data =3D cryptodev_globals.data[dev_id]; int retval =3D rte_cryptodev_data_alloc(dev_id, &cryptodev_= data, socket_id); cryptodev->data =3D cryptodev_data; ...............................=20 cryptodev->data->dev_id =3D dev_id; cryptodev->data->socket_id =3D socket_id; cryptodev->data->dev_started =3D 0;=20=20 cryptodev->attached =3D RTE_CRYPTODEV_ATTACHED; cryptodev_globals.nb_devs++; } .................... } in this function "cryptodev->data->dev_started =3D 0;" will executed in all= dpdk process which config with same dpdk crypto vdev, it's better add some condi= tion to set to zero, such as if the dev_started set to 1,dev_started not set her= e. would you please help to check and fixed it? thanks --=20 You are receiving this mail because: You are the assignee for the bug.=