From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 66EB542606; Thu, 21 Sep 2023 14:33:40 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5750D402D2; Thu, 21 Sep 2023 14:33:40 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 64D15402C5 for ; Thu, 21 Sep 2023 14:33:39 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 4BECF42607; Thu, 21 Sep 2023 14:33:39 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [Bug 1293] how to free mempool in secondary as prev process exit unnormally without calling free function Date: Thu, 21 Sep 2023 12:33:39 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: core X-Bugzilla-Version: 21.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: 779198444@qq.com X-Bugzilla-Status: UNCONFIRMED 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: multipart/alternative; boundary=16952996190.33558d3A.2058372 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --16952996190.33558d3A.2058372 Date: Thu, 21 Sep 2023 14:33:39 +0200 MIME-Version: 1.0 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 https://bugs.dpdk.org/show_bug.cgi?id=3D1293 Bug ID: 1293 Summary: how to free mempool in secondary as prev process exit unnormally without calling free function Product: DPDK Version: 21.11 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: Normal Component: core Assignee: dev@dpdk.org Reporter: 779198444@qq.com Target Milestone: --- hi, I recently using dpdk primary as a stable program that won't exit maybe= for a month, so i need do rx_burst in a secondary program,however, cause the secondary does a lot work and it may exit at any time,and restart, here is my question: 1.how to smoothly free or reset the ring,mempoop,zone and rte_ip_frag_tbl before my secondary process start up at next time? 2.what can i do to prevent memery leaking as my secondary process would restart many times? very much looking forword your reply. --=20 You are receiving this mail because: You are the assignee for the bug.= --16952996190.33558d3A.2058372 Date: Thu, 21 Sep 2023 14:33:39 +0200 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
Bug ID 1293
Summary how to free mempool in secondary as prev process exit unnorma= lly without calling free function
Product DPDK
Version 21.11
Hardware All
OS All
Status UNCONFIRMED
Severity normal
Priority Normal
Component core
Assignee dev@dpdk.org
Reporter 779198444@qq.com
Target Milestone --- 

hi, I recently using dpdk primary =
as a stable program that won't exit maybe for
a month, so i need do rx_burst in a secondary program,however, cause the
secondary does a lot work and it may exit at any time,and restart,
here is my question:
  1.how to smoothly free or reset the ring,mempoop,zone and rte_ip_frag_tbl
before my secondary process start up at next time?
  2.what can i do to prevent memery leaking as my secondary process would
restart many times?

very much looking forword your reply.

You are receiving this mail because:
  • You are the assignee for the bug.
=20=20=20=20=20=20=20=20=20=20
= --16952996190.33558d3A.2058372--