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 AF08BA2E1B for ; Wed, 4 Sep 2019 14:00:06 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id B74121EDA4; Wed, 4 Sep 2019 14:00:05 +0200 (CEST) Received: from mail-ot1-f49.google.com (mail-ot1-f49.google.com [209.85.210.49]) by dpdk.org (Postfix) with ESMTP id 29FF31ED8A for ; Wed, 4 Sep 2019 14:00:04 +0200 (CEST) Received: by mail-ot1-f49.google.com with SMTP id 67so8811970oto.3 for ; Wed, 04 Sep 2019 05:00:04 -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; bh=dXuICDiOo5Af1ERMf58XyXaSGOLNcMnFY350X8hfrjs=; b=Q5FOHX7Fptqhvm8iq2oO5d9fmMklw146Zx//j2j58YST63Qta86UkM0rMWmtXaJ6BV MwuP8pZV7rdT3BJiWTo8Foek5tiXNOp79yfOCiwQ1PZKkqq4gLMAdlXYsnS13V5OO4EH wS2mNSl9XS20eq65kcA3OzYn5NyDJLKRj28zDUqTeZ++yB/DZBacezCRqsCv2KRLgmgu l92duGyJEiy5Vs3tw19krgI997kDUGLmxQPQWSOKDW8uvd28pB+3e5eYNNLgf2OOwrak 6/2eLXpWPExtCpdjf31OH3DDgTG+k5GftsQOPrq4X2cp1TTTozr9L/k355Td020LkLBN jz6g== 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=dXuICDiOo5Af1ERMf58XyXaSGOLNcMnFY350X8hfrjs=; b=OmJrxF/GLlNzlbDAroxD+FeaYZzokKp97Vy8iCEdJyGHNbB63X3BfEwWpi4Y/QsCG0 R/G03ipB+L9PXbqa5fn2kee3Ynlv6R+Qv3jl3M0y4yuDi1Twa9gtrC4qsE+zdO5MyEIc IAuCgLH0bzkxQL4Mmy8zx0utCtUz9PVCPOrFjuP2DqJc2lZ+aBFy8LIgyek1ZATUA+Xm RdUlJ6VeAcSuywezv+kAC2MPVYPRB64D+Hwjyn/4V8AgBXhJ1luLNcKqO2AN6iBrt82S LFZvmaD5GI/4Ujs8XlDEOnThn3EA5UkDUP5wCobGVdTGnYp3zNveb21r54duek6U23wc 0oSw== X-Gm-Message-State: APjAAAWD84CcHMz7nG1geX8wV0NcO0Y3qGTzEPNAV7FJqyJLq3v2MyjU h/ly9l0dTBUVLfkTC1rB1HhmSfR2Prl5RXlg5zw= X-Google-Smtp-Source: APXvYqzJkQmtlFj8y0aMJfSyI8+hMQll809T13nypm9j2l9ZB9Vq/MteTyARZLfgkWt9D8lbBmT4S2o5Aqpq0X5zyjM= X-Received: by 2002:a05:6830:91:: with SMTP id a17mr11224318oto.322.1567598403338; Wed, 04 Sep 2019 05:00:03 -0700 (PDT) MIME-Version: 1.0 From: Byonggon Chun Date: Wed, 4 Sep 2019 20:59:52 +0900 Message-ID: To: "bg.chun@samsung.com" , "users@dpdk.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] Hugepages does not release after DPDK-App termination. X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 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" Hi, Forks. I found that the hugepages which took by DPDK lib did not release, after the termination of dpdk-app . Is this an intended behavior of DPDK so that should I give an option to DPDK? For more details, I pre-allocated 5 of 1GB hugepages per socket; I ran a sample on a 2-socket machine. Before running DPDK-app, each socket had five free hugepages. When a DPDK-app(testpmd or eventdev_pipeline) running on socket 0, one of the 1GB hugepages was consumed by DPDK lib on a socket 0. (so 4 of 1GB hugepages remained on socket 0 as free hugepages) After termination of DPDK-app, I expected that the 5 of 1GB hugepages would available on socket 0. But only 4 of 1GB hugepages were available on socket 0. Below is more information about my server and configuration. -The machine has 1GB NIC on socket 0 -set 5 of 1GB-Hugepages per socket -modprobe uio & insmod igb_uio -bind port to igb_uio I'm running DPDK samples in a following way: sudo ./testpmd -l 2,42,3,43 -n 4 -- -i --portmask=0x1 sudo ./eventdev_pipeline --vdev event_sw0 -- -r1 -t1 -e4 -w FF00 -s4 -n0 -c32 -W1000 -D Thank you.