From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by dpdk.org (Postfix) with ESMTP id 89F4A98 for ; Tue, 31 Jul 2018 18:37:19 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Jul 2018 09:37:18 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.51,427,1526367600"; d="scan'208,217";a="68968796" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by FMSMGA003.fm.intel.com with ESMTP; 31 Jul 2018 09:36:37 -0700 Received: from fmsmsx108.amr.corp.intel.com ([169.254.9.10]) by FMSMSX106.amr.corp.intel.com ([169.254.5.237]) with mapi id 14.03.0319.002; Tue, 31 Jul 2018 09:36:37 -0700 From: "Eads, Gage" To: "dev@dpdk.org" CC: "Burakov, Anatoly" Thread-Topic: Cleanup of secondary proc fbarray files? Thread-Index: AdQo61Qr3Z2yGLSLSF2gUeAgfVPRIA== Date: Tue, 31 Jul 2018 16:36:36 +0000 Message-ID: <9184057F7FC11744A2107296B6B8EB1E446F5E4D@FMSMSX108.amr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiM2Q2ZDhjOWUtMWI1MS00MWQ3LTkxMWUtYTY1ZDVhMWRlYjNjIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiVWM1elpFXC9ObkozWlowUVNqK3ZWaGN6WFVxZHVFTGlvdmxqamVzcThEOHFkb2tRSUFPQ1BKU1BHZEkyXC9SZHh3In0= x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [10.1.200.106] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] Cleanup of secondary proc fbarray files? 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: Tue, 31 Jul 2018 16:37:20 -0000 As far as I can tell, DPDK does not destroy secondary process fbarray files= - i.e. those whose names end with "_". With enough secondary processe= s and memory usage per application, and after enough repeat executions, the= se can take up a significant amount of space. Is the user expected to clean= these up themselves, or is this a bug in DPDK? Perhaps this is a good candidate for including in rte_eal_cleanup()? Thanks, Gage