From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id F2150A0528; Fri, 10 Jul 2020 11:22:30 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 2491F1DBB3; Fri, 10 Jul 2020 11:22:30 +0200 (CEST) Received: from mail-wm1-f54.google.com (mail-wm1-f54.google.com [209.85.128.54]) by dpdk.org (Postfix) with ESMTP id 7975F1DBAF for ; Fri, 10 Jul 2020 11:22:28 +0200 (CEST) Received: by mail-wm1-f54.google.com with SMTP id q15so5350627wmj.2 for ; Fri, 10 Jul 2020 02:22:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=Tv3N0wlKpLd3roxYGGm0kld9lE8egZ43HAf4hnIXOqk=; b=AkVzNU37I9O75ZU8mIkHLaAFgsb9TPEf5ClLn8o2klBciBf6Q58D8dI5HIQi5deHkD T59RqFKsyr0nsuPtjDA6FAZ5vAzO0BFanDKcZWJyS3+fEp31iZlPKqwlJNJyexeasB4X A+P8r2zlLoGEa4UPxz3H3BFVKVcRgQTjL8c1gnv6yb44utERhjEPhOPOaoaubSBlb8di c9QOIX60wC9y3iWoklqnFzg2HDGm0k0h4DA1xm84fOREYD9vScvhc4EX4vktBuYscMrq WynoAGobjMHrD7jE8ZhrUFeQ2mKhJ392e7u5rrvKT0krxJSv3B3s/TC3Xe0A8JbY5NZT XgDA== 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:cc; bh=Tv3N0wlKpLd3roxYGGm0kld9lE8egZ43HAf4hnIXOqk=; b=MF1rLLGwiPevJO7N8us6tUQcix7aVx+9CePZtQd7D3EXU1mYUJ3cWSSBM6iwXZvUks iVmFqIU6zb3myc8cuhfHov1gf/hHO3Xa2Nx4VtQHf5HIPVOOqbAjgTTESgfB5rMy42oh 0ovEwMnDX0jXGPMEvL0iA5ymOnGjvhKNtpoRPHVv2L9F2CWRMKm3kZ44NNUawguBw6QY veFmupM2zoEBkXHVok+P9iPHIppwPqbCrf7J1qBAyGPa0vCepmlHPjLwDeEtnTimauXc 1kDub8IFN0RILKYBsSmI0HjDGxDLI3rmgpFWMiSenn46mFHxDcAka6PwVlSuwrqjxTeT NAUA== X-Gm-Message-State: AOAM530ckLF9cj22y5f+gYn+AQNxTt9rdxcka3qqTVLbCKF151gWvY6b g0EYC2sCr4LIPh6yw0x4mlSRg6CQJ5KelS0Sk8+87qqH X-Google-Smtp-Source: ABdhPJz81rj9UGe+9w9J1K2Dgkg9VXjTv/psfJ9DsbrNqCYc8XayEne36y47ZCUGKbVVuTHYDYqX42dt3/1jY+q3UQE= X-Received: by 2002:a1c:4086:: with SMTP id n128mr4439545wma.118.1594372947429; Fri, 10 Jul 2020 02:22:27 -0700 (PDT) MIME-Version: 1.0 From: Kamaraj P Date: Fri, 10 Jul 2020 14:52:16 +0530 Message-ID: To: dev@dpdk.org Cc: "Burakov, Anatoly" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] DPDK hugepage memory fragmentation 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hello All, We are running to run DPDK based application in a container mode, When we do multiple start/stop of our container application, the DPDK initialization seems to be failing. This is because the hugepage memory fragementated and is not able to find the continuous allocation of the memory to initialize the buffer in the dpdk init. As part of the cleanup of the container, we do call rte_eal_cleanup() to cleanup the memory w.r.t our application. However after iterations we still see the memory allocation failure due to the fragmentation issue. We also tried to set the "--huge-unlink" as an argument before when we called the rte_eal_init() and it did not help. Could you please suggest if there is an option or any existing patches available to clean up the memory to avoid fragmentation issues in the future. Please advise. Thanks. Kamaraj