From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-out1.informatik.tu-muenchen.de (mail-out1.informatik.tu-muenchen.de [131.159.0.8]) by dpdk.org (Postfix) with ESMTP id F27596CC2 for ; Thu, 13 Oct 2016 16:56:59 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by mail.net.in.tum.de (Postfix) with ESMTPSA id 57D0D282F002 for ; Thu, 13 Oct 2016 16:56:59 +0200 (CEST) To: users@dpdk.org References: From: Paul Emmerich Message-ID: <54518164-0527-8328-dd72-a4c00c3a1b7a@net.in.tum.de> Date: Thu, 13 Oct 2016 16:56:58 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-users] Current CONFIG_RTE_MAX_MEMSEG=256 is not enough X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Oct 2016 14:57:00 -0000 Cliff Burdick: > I know I can increase this parameter in the DPDK config, but I'm not sure > why that's the solution and that it runs fine for so long until hitting > this. Should I just increase that, or is there another issue at play? The problem is memory fragmentation, a reboot might solve this. I've also got a server that gets this message from time to time and encountered no ill effects from simply increasing the config setting. Paul