From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 31BCBA0613 for ; Thu, 26 Sep 2019 09:55:25 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id EA5DB1BEC3; Thu, 26 Sep 2019 09:55:22 +0200 (CEST) Received: from mail-vs1-f67.google.com (mail-vs1-f67.google.com [209.85.217.67]) by dpdk.org (Postfix) with ESMTP id 165AD1BEC2 for ; Thu, 26 Sep 2019 09:55:22 +0200 (CEST) Received: by mail-vs1-f67.google.com with SMTP id m22so965030vsl.9 for ; Thu, 26 Sep 2019 00:55:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/PU6bBvjPOOAuxXaTiWkg+UwV4yaG8V1CjwKaqoguqU=; b=eesytcZfIgTO5WJsYF+CFf3z3NEAlFACAf1ySZKHK8qDzgQVnlK2GXAhPHtfSNCAfD B6MPJ3YkuMfImae6g/bRhABjlm4XEfOb9JjF+nxNltsDoJs1//fqQC3W4RIweKQgwz2p Ak9rm+2tXIjSv8Vem6EBE5XbHkLuB6Fv3O3xyCVVnUOKKzCTieYjrfN/tq52TnS8rmhW RFU/PaTHj8btFGOIFi80jXkpkFNmazXhRARFBhFAaiX6hrCiJh1SRpsbpplS7VWgOgSD DfqbzSzuma2xUeYwbwK+bIK4PU+JSqgN6BxX7tF8V4sbaIwuPVJNVhR5H+xnpvNUTjTw lRPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/PU6bBvjPOOAuxXaTiWkg+UwV4yaG8V1CjwKaqoguqU=; b=GBRlDbRiKqtPYGPg/vab2JLF++lUOzUQtRaCz7minP5XVX/kbTTzY/983MQ9cQraOR N2sf60MtqCmLbm6TilMh2Z0TXxQeiUsKcbF1jnvUJEGN7fuPqQ9675iebyKrpT4/AK2W GeFLd+KKMkdAyMZPOpkPNHqkGuGMAFgSNstYONNd1jLHftYg21taKLqWcOygZBc7Zn0C /lWuWxffOfeK/gFrIhVGNoiWl7FKV94fMU7l4QOS9tmPTSC05unjTKyJZ69/6+i/n2c+ tgI/MUgGCmOviuSPRP1pjlkQaPCIMG6vSC1m3dvD3I5WWx5F9VI7DyFGF/CaUeOS5pw7 IxUw== X-Gm-Message-State: APjAAAUb0inYMilZ1bQOnxgS15cTWZAuGaJDrro0eGup67FubdduQWsb eWyH2IsofaJDklygmmBs4bAxKnz5UgO4YF2okPM= X-Google-Smtp-Source: APXvYqx+gJGYsB0I7Z6Mkpru/upeRpsqRNbPNkr9OyLFbEJ169KpcltkrsxkQK8uW7D41l3r0/6M2uTMnmY1h/Sfils= X-Received: by 2002:a67:c181:: with SMTP id h1mr1026120vsj.195.1569484521165; Thu, 26 Sep 2019 00:55:21 -0700 (PDT) MIME-Version: 1.0 References: <20190925221637.11fb9632@hermes.lan> In-Reply-To: <20190925221637.11fb9632@hermes.lan> From: Gaurav Bansal Date: Thu, 26 Sep 2019 13:25:08 +0530 Message-ID: To: Stephen Hemminger Cc: users@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] packet drops seen once the no of rxd pkts reach the ring size 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: , Errors-To: users-bounces@dpdk.org Sender: "users" Thanks Stephen for the reply. I am planning to try that but that will require some major changes & lot more time, as this library is tightly integrated with our code base. Meanwhile please let me know if there is anything that can be tried on 16.04 itself. thanks, gaurav On Thu, Sep 26, 2019 at 10:46 AM Stephen Hemminger < stephen@networkplumber.org> wrote: > On Thu, 26 Sep 2019 10:45:03 +0530 > Gaurav Bansal wrote: > > > any suggestions here ? > > > > On Wed, Sep 25, 2019 at 4:09 PM Gaurav Bansal > wrote: > > > > > Hi all, > > > I am using dpdk 16.04 library to process the packets on a vmware vm > (say > > > vm1). The traffic is sent through a client machine using apache bench. > I am > > > observing an issue when the number of packets reaching the vmxnet3 > > > interface reaches the descriptor ring size (set to 2048). Till 2048 > all the > > > packets correctly reach the 'vmxnet3_recv_pkts' function. > > > > > > But as the number of packets received reaches 2048, i start seeing some > > > retransmissions on the client side (as shown by tcpdump on client > side). > > > Then i captured the packets on the esx host destined to vm1 and it > shows > > > that all the original packets as well as the corresponding > retransmissions > > > are reaching vm1. But somehow these packets fail to reach till > > > 'vmxnet3_recv_pkts' function (this was found by putting the breakpoint > in > > > 'vmxnet3_recv_pkts' function and dumping the packet contents, which > showed > > > that some packets don't reach here). > > > > > > Now 'vmxnet3_recv_pkts' is the first function which reads the packets > from > > > the descriptor ring and as the packets are not reaching till here, i > am not > > > sure on how to debug this further. Possibly some issues related to the > ring > > > initialization.... I enabled the init & RX logs for vmxnet3, but i > don't > > > see any error logs as well. I also tried looking at rxq stats and it > shows > > > 0 all the time : > > > (gdb) p rxq->stats > > > $1 = {drop_total = 0, drop_err = 0, drop_fcs = 0, rx_buf_alloc_failure > = 0} > > > > > > Can anyone please provide some clues on how to debug this further ? Are > > > there any known issues related to this which have been fixed post 16.04 > > > version ? > > > thanks, > > > gaurav > > > > > Try a newer version of DPDK first. >