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 F0084A0613 for ; Thu, 26 Sep 2019 07:15:17 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 305882BCE; Thu, 26 Sep 2019 07:15:17 +0200 (CEST) Received: from mail-vs1-f41.google.com (mail-vs1-f41.google.com [209.85.217.41]) by dpdk.org (Postfix) with ESMTP id 4D42F2B8D for ; Thu, 26 Sep 2019 07:15:16 +0200 (CEST) Received: by mail-vs1-f41.google.com with SMTP id v19so764842vsv.3 for ; Wed, 25 Sep 2019 22:15:16 -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; bh=GqT6WWTm6OIhxOYcXf3n2ugKMj12j0IOH9fKfR0gWdA=; b=jKCaNjt/cyaQKS4XMrVNBXIRUMSXtbKdmAnVcnMTPQ2Wm3DuvWi7TIh8qWIL+jKImy YMo6RYhmy0tfT0Ocyd6YgeIOgAfzy/Mur+QrHlufYADtj2miury+8E1V7z1GcG5Gi55X G3yKAXCk3L4AqjYJyTwBycbH2jctFKz8Na0UVTcGnf89g0n8sdUX/GPI2FWyQ3T91Qg3 TfUqvookp2ywFBeSfpb1Ds8Wwl+UgFISaOY7LqaByrqEITXayBzdviVZAZ8t4a0wrSx9 qX0GsMCpS9XzJ8izCmXjKGX+XXTZNIomx3u3FbCwGpdeU8G+un1bSNRk4QsFLZ209IOr 5hbA== 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; bh=GqT6WWTm6OIhxOYcXf3n2ugKMj12j0IOH9fKfR0gWdA=; b=bCJAK6lHIKruCacR3zwrbWaOAmWK9kGDcGYvlhn+bpO3zkwntqARoPkqCSi1kjqKba bRaHit8KAyCZCmb4QoCzKOrSw5xPMC6plcGWu/sTtBmRupz9nRdJfzpsfF561vh1IMCw ODs9cL0mkI4oGi2F3/imKM8zM0D9FCHqVTmA282y0nkQQ51pGs1+wX9xWD3JqjahfcKV PKudVo2dg+KO5dPblF6/25zVAZfIwMA7kCyZQ8ny3IJauDCM3zfhZrUPybV4QMqaHcgP txtJKzTR/SSh5MJRyg+q0hZ+uMq8Hrp3bJRuMTZkGXTRs92upNpqAyRSX+BMvXDo/YgH 5p3w== X-Gm-Message-State: APjAAAWA4iDIhn4kO5VrGZGzIlSXZmx8uEokfoNUBftajSLYYY3LhTg2 ezaWhp/a989Jmb1UnCu5pBWEOIWg7ipDZdrWbfxIkzvb X-Google-Smtp-Source: APXvYqwLajjiHuHl3qdZMny89lOMHa4NVq2dhyOmZxwxma3EJjeNR3l4YBf651BPQVQYDxzl/3tqpVVBJuiYUxr38Yw= X-Received: by 2002:a67:328f:: with SMTP id y137mr779829vsy.199.1569474915382; Wed, 25 Sep 2019 22:15:15 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Gaurav Bansal Date: Thu, 26 Sep 2019 10:45:03 +0530 Message-ID: To: 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" 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 >