From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-f42.google.com (mail-it0-f42.google.com [209.85.214.42]) by dpdk.org (Postfix) with ESMTP id B067E37A6 for ; Fri, 30 Jun 2017 22:38:06 +0200 (CEST) Received: by mail-it0-f42.google.com with SMTP id k192so30750033ith.1 for ; Fri, 30 Jun 2017 13:38:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=qW4jhzdYR/gp/BYjlNHJJh5/cvMb6glwUs0JH7Gpn3g=; b=BZWtUQ1NUV/NfqruDGM7PV+sPS3y3aO6v+IaPKyBNSXy5S98ojyf36Md47fTN9E+ea nyPxpahI+8sgy64RCl5e6gq/YbUFoF2pVUb2IhVcgXCqe8dn1nxJ2WkC/RhUO0p4+X+z VbLo0xQjMJ0rMPm1y65QETcLpgZRs3TrsE6LHGgKwV576PxgqL/o+NqQ0H+E2x5XMDVb XlSE/WgSGpAV041KQ/e1k46inMSdR7zWuiFjS+2eYyHvciJylPmTxrrQFtHdUhPCq7CT f8wrQy+q/w72NCBtfxWy5PgxkxUc8rmBVRIqPu0EpXlhf1kQ8nL/9x333vLp4SoWol4G oPwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=qW4jhzdYR/gp/BYjlNHJJh5/cvMb6glwUs0JH7Gpn3g=; b=s7jq7b+Tf/lPs0rLp5iB+IUTZvQ0ICt+TvT+EWkdWtUv20XXuGwUWpnG86zhdhPwpw LVuIJ5TrH+UlGs24kE97mq7mdsjhZcMlZTX6/vY/YfQUGQe0mssJ8d3knN2EDYsrO138 tuN72FH2aR9VP59FKJZhgAlatz/RyIpW/MprLciEr1P24xKIKPcYPuf3yNRBjuKYGMLG 5Eryoix1CWrR8w1Tou6dMTklAAp8MFzyk0F8B55W/Kg8tkP2JVSD0S2M7F6fC0Z6oB1o glq3n7V/TrHlBSwI+/PBnkvcffBNTVRAoUBKZDjOpEI3vS72s7uRSjOgeexSTH1dU1BW mfVA== X-Gm-Message-State: AKS2vOwPG9n1ba0K0vm7lzDxZpdMun6YdlIrOXGEheRsazC9/Iv8SQl4 GgBxereQpOJZ7vQj5glVkub5ru6UmlQp X-Received: by 10.36.206.133 with SMTP id v127mr9831414itg.49.1498855085690; Fri, 30 Jun 2017 13:38:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.146.2 with HTTP; Fri, 30 Jun 2017 13:38:05 -0700 (PDT) In-Reply-To: References: From: Cliff Burdick Date: Fri, 30 Jun 2017 13:38:05 -0700 Message-ID: To: users Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] Wrong Data In Buffer After Upgrade To 17.02.1 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, 30 Jun 2017 20:38:07 -0000 Hi, after debugging this more, it seems like vector PMD mode for the i40e driver in 17.02.1 is what's broken. If I disable that option, my code works fine. Does anyone know if this is a bug, or possibly just an issue in the way I'm using it? The feature was turned on by default after 2.2.0. On Wed, Jun 21, 2017 at 8:42 AM, Cliff Burdick wrote: > Hi, I upgraded from 2.2.0 to 17.02.1 using the i40e driver, and I'm seeing > very weird behavior that's easily reproducible. My receiving thread/lcore > calls rte_eth_rx_burst(), changes the endianess on some of the packet > headers, and puts the pktmbuf onto a ring for the next eal thread to > process and eventually free. After upgrading, I'm seeing that > when rte_eth_rx_burst starts reusing buffers from the mempool, it's > returning buffers that don't have the new packet's data, but rather the old > data where I had already changed the endianess on some of the headers. I > removed the ring part, and even doing: > > 1) rte_eth_rx_burst > 2) Change endianness > 3) free pktmbuf > > all within the same thread causes this issue to happen too. I've looked > through the changelog and don't see anything obvious that would be causing > this. Has anyone seen this happen? Thanks >