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 069B4A0546 for ; Fri, 19 Feb 2021 20:18:53 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 78CB916097C; Fri, 19 Feb 2021 20:18:53 +0100 (CET) Received: from mail-lj1-f177.google.com (mail-lj1-f177.google.com [209.85.208.177]) by mails.dpdk.org (Postfix) with ESMTP id 09FD5160979 for ; Fri, 19 Feb 2021 20:18:52 +0100 (CET) Received: by mail-lj1-f177.google.com with SMTP id q14so26108198ljp.4 for ; Fri, 19 Feb 2021 11:18:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=CtuPIl7FXrH9WsOo4dYQwo1g0wFEkmq5i0I5wsRpyyg=; b=SYq4QUcyrGuI+cRGSfn5LO/YjzXtcr8nAYqb3jafyurUH51ib6/m2d/iIPM0FZQtPI Le5FfNC5dCNIoSlkUUglzwF8J0CNb1o+RZoVoGJ2lvx0+gfBGDBacdb8kGblCefeERcs Aw0lGGui6tiUYYA+gogUJpMZ/j3lYb5fJkWwyEvMD3FcBiQf3n+Oh9O9fE8kr/UptdYT t/hR05NGH0kcnrnZq7qvCvgtDGlKg+DC8SxdjeJd79y9guvzuTn2BW/mzHJ1pIdcgRMI Z6/efeZItDhEZ+QwWND19zSob2PDCxBYLkOJ+rJiFVaRPTVEpdK5YMyZ7enJRWzIEKFg wjQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=CtuPIl7FXrH9WsOo4dYQwo1g0wFEkmq5i0I5wsRpyyg=; b=JIICY2CiZgMn03KDxl0GQoP9mQJ9h//SguGUva+otk3mKVugvjOfKPzNb4gfj2BB/e oviDlxWH9fvWUbYH9RZh/plIYY+t7IWOGGRqNFTWwr0YbM+wRa/Ybl9iWW2m9sdjzw6G zrkHIjnSRxlaKTJx4LLwJYdGJyshlaTROMYVNHWP5N1FMx+V6yVJOHH1sf4J/1sqyWQ1 zc3+6aThyM+6vfVL6RYclVg56PiOsD7nOZ24j9TrmdfM0p88I1doVO/DNRdKTPRZiAfQ mNyzrkecSWb5I00cZ8YuN4rEu4zMf5qK/+28WQiwMjtnCZajXOUf/cQzJDOrNqDO8XL2 7piQ== X-Gm-Message-State: AOAM531k9VqQT/prnP6PUjkVjualbVv21Og6nok+G/n7RgeiI74LWrPl Iu6d7eYvCvQ9ZNVhJ9ysBiWM2a0Nvo8eGtxe9H5mBKdTX8zjNucB X-Google-Smtp-Source: ABdhPJzSR9A2X0WPVSEWYYRfLFYe35V4dJOPh/R+6dp1FG27Zwjj1ARZb5F/F2V+r2Kok/WFLiGQ/RAyW7hgQH0MpQo= X-Received: by 2002:ac2:5962:: with SMTP id h2mr133445lfp.311.1613762331032; Fri, 19 Feb 2021 11:18:51 -0800 (PST) MIME-Version: 1.0 From: James Huang Date: Fri, 19 Feb 2021 11:18:39 -0800 Message-ID: To: users@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: [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" On CentOS7, we observed that the program (based on dpdk 19.11) creates 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 hugepage 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