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 3A517A034F for ; Thu, 25 Feb 2021 18:37:54 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A6800406B4; Thu, 25 Feb 2021 18:37:53 +0100 (CET) Received: from mail-lf1-f48.google.com (mail-lf1-f48.google.com [209.85.167.48]) by mails.dpdk.org (Postfix) with ESMTP id ADB6A40692 for ; Thu, 25 Feb 2021 18:37:52 +0100 (CET) Received: by mail-lf1-f48.google.com with SMTP id u4so9820160lfs.0 for ; Thu, 25 Feb 2021 09:37:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RrArWKscNy67Q38tPpTifLSnXA/CEGwIqqTcwBlvTi8=; b=dCZ06PqfaSCwd84HRkZ7vbyRF2yZ5N6fF/t3zGtVQomzFZQvEPqdlVAqNtqK4cQzcA mn5V1ptcTWdnteCJu9X/KaxI6dcZ1X+4JJMHyvhGJTi9Jz1gyO9pun7dt2XuXG5a019t yxH9TgQaFRYmw179YfDWqhu1yqzJ0pUP5JQvN4DbRA+spjCLev/5DDMU6xOVrPkrnVz7 +e/Ku8bOJ9bOv4t52w1Qs9qlf1LxVBmmsX6bnsIPm4amVr3ZcmqIVHz3oPFJJWhHFpCA 3JphdMjItTUZqZjsXDtbk52ObWsKG+xmE6OcmjWC+KKD1wbo5z1RrrdQ8pU6hvX+zh+5 NRZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RrArWKscNy67Q38tPpTifLSnXA/CEGwIqqTcwBlvTi8=; b=BL9v6Y1J5Wnifwt8px9gmdDR4ByqwbECWRKxLJNw53Ab0g9P+4gKcFd09go5M/ZBNx VVpccWxEnbsUmlQ69S+lKGYOsSHlg+sg4wTTWwTcKIzlV4VXlsqSwA24JGGkIduyK4B5 NY18v9BR3uGronGWT1OxsCjB0Oqn86Xlin+ytMi2Q7sPaKQF6XaMAsIYRHqmM581TsHI AokzWgpfpHhLOawjndo9p3FTmS1+0MLrS8s+9Q8Hq02JLQmDRfVXEyqXwuY7Uj/atUI/ DPA+ynpZGYSJgCu7IseFRfK3E0Sl32+HsTQ1cGBJR28KknPh4YnMzoIiLyatoinPGqWq 2SGg== X-Gm-Message-State: AOAM533hkxCLFVnHSfK4bDfjVD5fHZIE0sSBrVx4j/4+KaeB44jkSByv kbcOVcEHFVI7NewSvyNaouVFKRah9mBUKyC0GjX7g6DIXfF0NuuN X-Google-Smtp-Source: ABdhPJx6R3M3ssqgwqJaH1Uw9Vw97p+mPPbi2nx919Y1zjPGNM1ShJloL6X3mOGZv2vzG5Jsr5BCXz7/V9tO5NPpq2Q= X-Received: by 2002:a19:98a:: with SMTP id 132mr2498022lfj.139.1614274672035; Thu, 25 Feb 2021 09:37:52 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: James Huang Date: Thu, 25 Feb 2021 09:37:40 -0800 Message-ID: To: Li Feng Cc: users@dpdk.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [dpdk-users] DPDK program huge core file size X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" @feng, thank you for the info. We'll pull the fix from eal_common_memory.c:eal_get_virtual_area(), give it a try. Regards, James Huang On Tue, Feb 23, 2021 at 8:00 PM Li Feng wrote: > I think you should update your dpdk to the latest. > I have fixed this issue some months ago. > > d72e4042c - mem: exclude unused memory from core dump > > Thanks, > Feng Li > > James Huang =E4=BA=8E2021=E5=B9=B42=E6=9C=8824=E6=97= =A5=E5=91=A8=E4=B8=89 =E4=B8=8A=E5=8D=883:22=E5=86=99=E9=81=93=EF=BC=9A > > > > UPDATE: the 'kill -6' command does not dump the hugepage memory zone in= to > > the core file. > > > > Is there a way to bypass the hugepage memory zone dump into the core fi= le > > with running gcore command ? > > > > > > On Fri, Feb 19, 2021 at 11:18 AM James Huang wrote= : > > > > > On CentOS7, we observed that the program (based on dpdk 19.11) create= s > a > > > huge core file size, i.e. 100+GB, far bigger than the expected <4GB. > even > > > though the system only installs 16GB memory, and allocates 1GB hugepa= ge > > > size at boot time. no matter if the core file is created by program > panic > > > (segfault), or run with tool gcore. > > > > > > On CentOS 6, the program (based on dpdk 17.05), the core file is the > > > expected size. > > > > > > On CentOS7, we tried to adjust the process coredump_filter > combinations, > > > it found only when clean the bit 0 can avoid the huge core size, > however, a > > > cleared bit 0 generate small core file (200MB) and is meaningless for > debug > > > purposes, i.e. gdb bt command does not output. > > > > > > Is there a way to avoid dumping the hugepage memory, while remaining > other > > > memory in the core file? > > > > > > The following is the program pmap output comparison. > > > on CentOS 6, the hugepage resides on the process user space: > > > ... > > > 00007f4e80000000 1048576K rw-s- /mnt/huge_1GB/rtemap_0 > > > 00007f4ec0000000 2048K rw-s- > > > /sys/devices/pci0000:00/0000:00:02.0/0000:04:00.0/resource0 > > > 00007f4ec0200000 16K rw-s- > > > /sys/devices/pci0000:00/0000:00:02.0/0000:04:00.0/resource4 > > > 00007f4ec0204000 2048K rw-s- > > > /sys/devices/pci0000:00/0000:00:02.0/0000:04:00.1/resource0 > > > 00007f4ec0404000 16K rw-s- > > > /sys/devices/pci0000:00/0000:00:02.0/0000:04:00.1/resource4 > > > ... > > > > > > > > > on CentOS 7, the hugepage resides on the process system space:: > > > ... > > > 0000000100000000 20K rw-s- config > > > 0000000100005000 184K rw-s- fbarray_memzone > > > 0000000100033000 4K rw-s- fbarray_memseg-1048576k-0-0 > > > 0000000140000000 1048576K rw-s- rtemap_0 > > > 0000000180000000 32505856K r---- [ anon ] > > > 0000000940000000 4K rw-s- fbarray_memseg-1048576k-0-1 > > > 0000000980000000 33554432K r---- [ anon ] > > > 0000001180000000 4K rw-s- fbarray_memseg-1048576k-0-2 > > > 00000011c0000000 33554432K r---- [ anon ] > > > 00000019c0000000 4K rw-s- fbarray_memseg-1048576k-0-3 > > > 0000001a00000000 33554432K r---- [ anon ] > > > 0000002200000000 1024K rw-s- resource0 > > > 0000002200100000 16K rw-s- resource3 > > > 0000002200104000 1024K rw-s- resource0 > > > 0000002200204000 16K rw-s- resource3 > > > ... > > > > > > Thanks, > > > -James > > > >