From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ig0-f176.google.com (mail-ig0-f176.google.com [209.85.213.176]) by dpdk.org (Postfix) with ESMTP id 6E1345A76 for ; Wed, 11 Mar 2015 16:53:45 +0100 (CET) Received: by igdh15 with SMTP id h15so13390979igd.3 for ; Wed, 11 Mar 2015 08:53:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:content-transfer-encoding :subject:message-id:date:to:mime-version; bh=AwiZyZVAwnjqA6g3BFJj0G/XAd4aoG7Npgl8+hmBctQ=; b=YtKtAdqZMgiA3shl1ZFsl61LHGsHgzWLJywedcxRQadoXol7GV11KriJ2Sg0aAWSzK Y+ELcnwBdFCpBtdsNa3KvKUpy32IjlIu8vyeR4Fj1XGA4rsRYwqNxvKXXs4n6TAA/nu7 OG/ROfATBqh2SKLd9jSOreUmFLl5LrKHqrpE/6o0WGsWbobpjH4wFQCtxlPM+OjgytY7 zG69rEcQ9Ig9YaqZwZxyrnNnz4q4DvoYCguBaURHoiPEpiAQKyvxxztLPh36+UF3GCvw cxLSXsGPnn066EsR3lpwaE4neF7miP8ys9SwFstEgAxNImz+mLYnroqDZD0rEaI+EONp QnWw== X-Gm-Message-State: ALoCoQmHk9dPfLixryTIwp3PNu8CE+jYTbVbZGoUkiK+JTB55LGagWtpi68BC6ibZDcvoGbLsK2/ X-Received: by 10.107.165.68 with SMTP id o65mr49253415ioe.56.1426089224650; Wed, 11 Mar 2015 08:53:44 -0700 (PDT) Received: from [10.0.2.33] ([209.119.128.34]) by mx.google.com with ESMTPSA id m132sm2647678ioe.33.2015.03.11.08.53.42 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 11 Mar 2015 08:53:43 -0700 (PDT) From: Dennis Montgomery Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-Id: Date: Wed, 11 Mar 2015 11:53:44 -0400 To: dev@dpdk.org Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) X-Mailer: Apple Mail (2.1993) Subject: [dpdk-dev] How can I recover from CONFIG_RTE_MAX_MEMSEG overrun? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 15:53:45 -0000 Hello, I=E2=80=99m running into an occasional problem where rte_eal_init() = returns -ENOMEM and the following error is logged: EAL: Can only reserve 991 pages from 1024 requested Current CONFIG_RTE_MAX_MEMSEG=3D256 is not enough When this happens a reboot will take care of it, but I=E2=80=99m hoping = for a more elegant solution. I don=E2=80=99t have much direct experience = with hugetlbfs so I=E2=80=99m hoping someone on this list can suggest = something. I did boost max-memseg and it works, but I=E2=80=99m worried that it = will just crop up again - I instrumented rte_eal_hugepage_init() and = found that the number of segments used slowly creeps up as I cycle my = application (i.e. repeated rte_eal_init() invocations with process-type = =3D=3D primary). I=E2=80=99m theorizing that hugetlbfs fragments (for = lack of a better phrase) over time. Does anyone on the list know of a = way to reset hugetlbfs short of rebooting? DPDK version: EAL: RTE Version: 'RTE 1.8.0-rc0' Linux version 3.16.6-200.fc20.x86_64 = (mockbuild@bkernel01.phx2.fedoraproject.org) (gcc version 4.8.3 20140911 = (Red Hat 4.8.3-7) (GCC) ) #1 SMP Wed Oct 15 13:06:51 UTC 2014 Thank you, Dennis Montgomery PS this is my first post to this list; apologies if I=E2=80=99m = violating any protocols.=