From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-f170.google.com (mail-ie0-f170.google.com [209.85.223.170]) by dpdk.org (Postfix) with ESMTP id C61B4ADBE for ; Wed, 25 Jun 2014 03:31:39 +0200 (CEST) Received: by mail-ie0-f170.google.com with SMTP id tr6so1055695ieb.15 for ; Tue, 24 Jun 2014 18:31:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Lukl3Nzj1BOdbwN8B94LFxsRa/6jz9M9vXyKjNxdxw4=; b=EIBXxz1mbmRmFqTxBfSDzzLUK4jKw5txKB0FRUeW9DH9Dh9W5tcDGjliIwRb+pIehY oW6QEWdeL2OGB+jfirlhXmoMARzYsyV3sRJvm9J/YB4kCnT4DfbFKCKfQN6IX5tX0Vp0 KAHWvYJuw95BNAl2NVSZyYCIlDHf2qU+NLqsEwUKwn3eW7A5TN9gU9ZuCOH8PJ29R+C2 nieBTAfpNNI7Uhvt6XnCvuYKidf20+3/NVkSM+t2fsUwLBxD/9LlgL58TU5RwNmXqthp p0CLMLkFz1b8gC8jk6oUSFG67dtBLAhi9leTo4Qoo3u+VTp9IL35EYZikCxpucbzbDVW A9Yg== MIME-Version: 1.0 X-Received: by 10.50.56.15 with SMTP id w15mr6054519igp.30.1403659917725; Tue, 24 Jun 2014 18:31:57 -0700 (PDT) Received: by 10.64.28.18 with HTTP; Tue, 24 Jun 2014 18:31:57 -0700 (PDT) Received: by 10.64.28.18 with HTTP; Tue, 24 Jun 2014 18:31:57 -0700 (PDT) In-Reply-To: <53A95AA3.90408@6wind.com> References: <53A43E5E.3030809@windriver.com> <20140624104859.GA19229@hmsreliant.think-freely.org> <53A95AA3.90408@6wind.com> Date: Tue, 24 Jun 2014 21:31:57 -0400 Message-ID: From: Stefan Baranoff To: dev@dpdk.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] Random mbuf corruption 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, 25 Jun 2014 01:31:40 -0000 Thanks, all! We have alloc/free counters in place but I'll enable those debug options. I'll try older releases of RHEL and get back to you. I've also eradicated pthreads in this code but also have the mempool cache size set to 0 just in case. I should mention we hold onto mbufs for a while (up to 30s) and have many of them available (~8GB worth at 2K per). The entire app is fairly short (2k-3k lines) so it's not too hard to review. We'll take another look for buffer overruns. Thanks, Stefan Sent from my smart phone; people don't make typos, Swype does! On Jun 24, 2014 7:02 AM, "Olivier MATZ" wrote: > Hi, > > On 06/24/2014 12:48 PM, Neil Horman wrote: > >> Sounds like it might be time to add in some poisoning options to the mbuf >> allocator. >> > > Such option already exists: CONFIG_RTE_LIBRTE_MBUF_DEBUG and > RTE_LIBRTE_MEMPOOL_DEBUG will enable some runtime checks, at least > double free and buffer overflows. > > Olivier > >