From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id B9A68A050A for ; Sat, 7 May 2022 18:55:30 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4087D40DDB; Sat, 7 May 2022 18:55:30 +0200 (CEST) Received: from mail-yb1-f178.google.com (mail-yb1-f178.google.com [209.85.219.178]) by mails.dpdk.org (Postfix) with ESMTP id 75C1E40395 for ; Sat, 7 May 2022 18:55:29 +0200 (CEST) Received: by mail-yb1-f178.google.com with SMTP id j2so17987625ybu.0 for ; Sat, 07 May 2022 09:55:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=JVLaNB2WK5OIdrj5vOUTZfjUO9u6pR4b/xjhwA1UZGQ=; b=SB3YNYPMbPsXQ0NMpo7bjJq4HSfIg8RJNPjyYX6Vzda20QDUJFyDUkE/0WVuuOc2mJ D4Xnbwap4jfXYNwK//uctPjiaQodNy8zbznRxRpFRct54HVB+hmr7HoFnhAxR2KUgOa6 TEcngllxuyFJTjaL5Ic1vJlapyIuF1scPYTc/xfs3JC3MjVBustwt9NDMVF49dZMYiO+ mWGw7A94S8zqJvLneYRMzs750oyh7JpUyuaHQoraJtXTstuIliOC0yAyoPnrKacxX2UI XiOAa7y3gA1zwdOjJ0TLikU5aLS2PwNM+v8nfhtImjrgK2HETlVlc1uxnYF930CXPzR3 aR4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=JVLaNB2WK5OIdrj5vOUTZfjUO9u6pR4b/xjhwA1UZGQ=; b=wgJaktyBXHWaYolS7x6P8uZJIGIyAReRUFXuF8qNI/GPrvu5XhMsyVVMRWG6MRC179 MsdEj5p9LoDvY0xZWpm+jERWh3yJBPfqQNFWyuCWUyAhMxQ1WlWBk6qdSknwKqOrQOPw bTT9MKRSyQ9/jpT2nj5nlTIxNRWUXIBqVrq5pjGnTR35THvhT+NkkZtoOiV6TVtQp5fn eI6nVJ5YSquIoegDaNVmJD8Ein3opcUsZeu/OtPKXoYFwpvUsAM0GaGX1ecsYL+MHPyw h0NhiSkQ7K5W1sdI9RyQItjOy9qzIF/MNPmSiLG7xQuS3xdBxPf1jsS9wbGQsBfZLMl1 wkFQ== X-Gm-Message-State: AOAM531qU5x/UIvuhKD7EYOBLyLwcEVgyJCun48Bymme0qRzs6lV7fte vqzz/crpT8jaH00m9VEmKn3CpQTeXMBa9Qv9lSE6uAm/JQ== X-Google-Smtp-Source: ABdhPJzDGlDjUirnHvRHSXbetV3pHsL09hz8Gbzy5IqbjW9rb2ZxxyaXefCtXaktEqA02ngaYZawm/3w4+EFIkZUpOk= X-Received: by 2002:a25:fc6:0:b0:649:96cc:1213 with SMTP id 189-20020a250fc6000000b0064996cc1213mr6847539ybp.119.1651942528617; Sat, 07 May 2022 09:55:28 -0700 (PDT) MIME-Version: 1.0 From: Laurent Dumont Date: Sat, 7 May 2022 12:55:18 -0400 Message-ID: Subject: DPDK and packet loss troubleshooting To: users@dpdk.org Content-Type: multipart/alternative; boundary="0000000000009b915205de6ed75d" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --0000000000009b915205de6ed75d Content-Type: text/plain; charset="UTF-8" Hey folks, We are troubleshooting a vendor application that is leveraging DPDK at the application layer. - Openstack with RHOSP / RHEL - OVS as the underlying virtual switching layer. *The VM is not using SRIOV ports.* - VM acts as a load balancer (traffic pattern in IN+OUT). Traffic arrives on a VLAN (provider network) and exits through a VXLAN network (internal) to be forwarded to application servers. - VMs are using pinned cores - 4 cores total - 2 for the OS - 2 for DPDK : 1 TX one RX - Using hugepages - There are no other VMs on the physical compute. - compute is using isolated cores for the OS. No collision with the VM cores. At low packet rates (20k~ PPS), it seems that the DPDK layer fails to transmit packets on the TX queue. This triggers a failover. We are not seeing anything particularly obvious on the compute side. Is there anything at the DPDK layer that should be clear about why there is a failure to TX? Thanks! --0000000000009b915205de6ed75d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hey folks,

We are troubleshooting a ven= dor application that is leveraging DPDK at the application layer.
  • Openstack with RHOSP / RHEL
  • OVS as the underlying virtual = switching layer. The VM is not using SRIOV ports.
  • VM acts as= a load balancer (traffic pattern in IN+OUT). Traffic arrives on a VLAN (pr= ovider network) and exits through a VXLAN network (internal) to be forwarde= d to application servers.
  • VMs are using pinned cores
    • 4 = cores total
    • 2 for the OS
    • 2 for DPDK : 1 TX one RX
    =
  • Using hugepages
  • There are no other VMs on the physical compute.=
  • compute is using isolated cores for the OS. No collision with the = VM cores.
At low packet rates (20k~ PPS), it seems that the D= PDK layer fails to transmit packets on the TX queue. This triggers a failov= er.

We are not seeing anything particularly = obvious on the compute side. Is there anything at the DPDK layer that shoul= d be clear about why there is a failure to TX?

Tha= nks!
--0000000000009b915205de6ed75d--