From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f49.google.com (mail-pg0-f49.google.com [74.125.83.49]) by dpdk.org (Postfix) with ESMTP id 4EB552C24 for ; Fri, 22 Sep 2017 19:09:45 +0200 (CEST) Received: by mail-pg0-f49.google.com with SMTP id m30so905049pgn.6 for ; Fri, 22 Sep 2017 10:09:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudsimple-com.20150623.gappssmtp.com; s=20150623; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=kf3a528xotnnMICJn9s/mHgyO0HKvAxXfuNbj3kV0MU=; b=DpjnVeSLpVG7EaZ0J2inMRb98ewc3E859LVzv9dqs5m3rlHSMogWRCgOQzGshWIj3j mphj4wcvbzvJBdWgYNlJYPBjhAStgEN3LoWWZhMJkDx4yT5tYy5AyQqAA7EHYlWFJQIi gGqsmAW0oZ3D7d0QKsS9nTyH8RudDOejM+dQ25uKat5BTxMKXT78ZFCoAskycnoL9PGJ eoFuV+DbEurWzNliEpwPXGJc7AyFNGIFwFFb5p1PzdBCsyqUSDrpZH/2uEJOWTNI2NSf 5Pvnoo+BlQMTraQQ4VGKPrfma2omWFjnTSfFixzYGpRq/Sqe1A55zLbCUd3NeoQrjTEB 1kDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=kf3a528xotnnMICJn9s/mHgyO0HKvAxXfuNbj3kV0MU=; b=C/1iTZOVM3dqfrOtzlPmLC9MIwhhd77qhtOX3dHTBznKNxd9XbDS6WFVZ99xq3exCG g7XEukHpzqMNzpcf+HyoaTShqPZuLf9tQochauyVp0m+srJu41fx80ZoCZKsdohSkEdv tTGVw9LdMTglNaRJzTbCMw0A4Pg0qtJ/tKZY8nOhGSn9xHVB2GpzRfIUgBMfpDHwB6F0 wcXDHQGEr2cWCyr1I4/FOeQU/GsJGPxS68FxAYX9Lfxxbqj1L+ZpOlwBszepg7Dg9lKF qFPDkV3QxQOCZkObz4DVlQWia8BpqjdbRxBrIrTvjGY5gRFwCDh0kCR29DV+tnTM4xsL ORkg== X-Gm-Message-State: AHPjjUhgT3b6v+cKz6JYXmfYUWSRxgaShZBksRX2UmcDz/+S+FPu5i03 FCunx8Er1ovQfBLuScejJkxLpdCKJQ/gxwDPoLfSms3w0i00//sf+djBISF1eJWOr+HRhc770bf TRKW+aKK9MoVc4dK7mBAk0EJH8MOQPPEw0/DiZeXlcgsvjZSLGb8mW9EKUtg= X-Google-Smtp-Source: AOwi7QBDV7pvsCDx0v7Q/nIUPjqviUvdFSQ4hOqpZ0moeZpCHZyuhNvQMSo5SeezxCgxCE4MxqZEwQ== X-Received: by 10.84.216.6 with SMTP id m6mr9844509pli.143.1506100184098; Fri, 22 Sep 2017 10:09:44 -0700 (PDT) Received: from ?IPv6:2405:204:5700:8ffe:38b9:c676:1cb5:6ee5? ([2405:204:5700:8ffe:38b9:c676:1cb5:6ee5]) by smtp.gmail.com with ESMTPSA id p20sm428592pfl.124.2017.09.22.10.09.41 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Sep 2017 10:09:42 -0700 (PDT) From: Kumaraparameshwaran Rathnavel Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Message-Id: Date: Fri, 22 Sep 2017 22:39:37 +0530 To: users@dpdk.org X-Mailer: Apple Mail (2.3273) Subject: [dpdk-users] DPDK Memory Allocation 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: , X-List-Received-Date: Fri, 22 Sep 2017 17:09:45 -0000 Hi All, We have been using DPDK for quite sometime. First let me tell my = assumption on how the DPDK works. For the DPDK memory allocation we give = size in terms of MB. When this size is given the rte_eal_memory probes = for the sysctl files and figures the starting Physical address of the = huge pages. Depending on the size given some number of huge pages should = be available. So whenever the memory is not contiguous different = segments are formed and each segment is contiguous. The Physical = addresses are memory mapped and heap regions are formed and rte_malloc = returns the memory from this Heap. We give 2GB to our application and the rte_eal initialisation takes = place successfully. But in the application the rte_malloc fails. This = happens randomly When we reboot the system we don=E2=80=99t see this = issue. So my doubt is why does this happen, DPDK memory initialisation = is successful but the memory allocation fails. We are sure that = application has not consumed 2GB of memory. Is there any condition that = we should reboot the system for every run of application that uses = DPDK.Should we do anything when we restart the application say some = cleanup after the first run. Thanking You, Param.=