From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <odeme@druidsoftware.com>
Received: from mail-io1-f42.google.com (mail-io1-f42.google.com
 [209.85.166.42]) by dpdk.org (Postfix) with ESMTP id 2FCE92B92
 for <users@dpdk.org>; Tue, 20 Nov 2018 18:18:41 +0100 (CET)
Received: by mail-io1-f42.google.com with SMTP id l14so1795172ioj.5
 for <users@dpdk.org>; Tue, 20 Nov 2018 09:18:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=druidsoftware.com; s=google;
 h=mime-version:from:date:message-id:subject:to;
 bh=lfvabcj531NwE6VbSnAPUJoa+mTat2wiHJZ7Enwz41k=;
 b=DFGaM8zneq06UADNNIT+mcZSs/Rplfn7PdiGj6wr38vkYVRm6jx7L6IfEyvEZc3x7D
 gpTtvE9+aEKk0atvejt1iKQ1bH28G3xpFO5YIQwXoUjuAz5bnVsifea7FvoQ2u16yOII
 L1ow0LN3DqZl6ZiRWe4lmktE+kt8zVvWUMUEMGxqRUNn2uAaEyQsl/ftDjOrbnFXnwPr
 ztGwL0Joxrlvu5LVaELptkL3Zqf95+RWJ6G7LBw2FCbUw1PsisNGxUCsO1u9AZbyzTfB
 uKPs3xhIyR01gvAWnPjO7KfwdgJDzNoEuxd6cW5PCplkF3mgoLVVAePfJNMx1Sns3Vyk
 zI1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=lfvabcj531NwE6VbSnAPUJoa+mTat2wiHJZ7Enwz41k=;
 b=N1nlOIUsLRKc9MftjtC6h0LWIeQ0X22d/XyOrUz2w19HK7lS+9bfcCp24AZspspC+C
 9F+wt/JFIGObHwkXUQ/zfYauWKUSAMBNgu4OdKVYKmeP2+ViXNJHa1m+A5acbojNII9m
 XW1DWXkpyBXh8xJ+hGdvQSZFoqrMc3XuTjn4c3TiOntmik+LVmfoA/MT/k2IGcPoRcoQ
 n4tESpJW4iuhBC9qAzv7oK0FwtsQixk4GApKaa0kkfjTIFqM1KtgQHFj8sAj3SFomQN7
 fnz2pf5LRyksxrwXsJVDKGLeZ5Yx4qMKeMcmxjoDtVz+6qCvl4rTjV8Bi8+8YdVQhSkt
 ua3w==
X-Gm-Message-State: AA+aEWYW4IBWl+au0b4hAu7iD5vDS4p/VaEDfV7YWmK7Zo75JwMgvfbn
 gkNo9SZM0mefQ47mbpky7dkJaeVX8fqrFmPJjaYY9DjJFa6uFA==
X-Google-Smtp-Source: AFSGD/XFLbJrW4Y2uD2ABCjVeJdZ0rPS/R9DyZNpBoqlwNBMe+SWd4LhusfN8u5ZNivYwiEYVFJOgybeao7g4syYWg0=
X-Received: by 2002:a5e:9916:: with SMTP id t22mr2249887ioj.153.1542734320290; 
 Tue, 20 Nov 2018 09:18:40 -0800 (PST)
MIME-Version: 1.0
From: Olivier Deme <odeme@druidsoftware.com>
Date: Tue, 20 Nov 2018 17:18:29 +0000
Message-ID: <CAAfggZOwqfD4UkSrkg6APjPn4ZgNRERHAw_A7BmJ3moinUAkqQ@mail.gmail.com>
To: users@dpdk.org
Content-Type: text/plain; charset="UTF-8"
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-users] rte_eth_tx_burst keeps returning 0 upon reaching TX
	throughput
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2018 17:18:41 -0000

Hi,

I am currently experiencing an issue with our DPDK application
whereby rte_eth_tx_burst keeps returning 0 upon reaching a certain output
rate.

Our application is based on the run to completion model.
Packets are read in burst using rte_eth_rx_burst, processed and then sent
in burst by the same lcore using rte_eth_tx_burst.

An external application generates test traffic.

We are currently using only 1 lcore and trying to verify how much traffic
can be switched on that single core, before testing with multiple cores.

Everything appears to be working fine up to around 5Gbs of traffic.
But then, upon generating more traffic, we observe that rte_eth_tx_burst
starts failing consistently by returning 0 on every call.
We checked that the mempool has many free mbufs.
We also observed that when the problem occurs, a call to
rte_eth_link_get_nowait indicates that the link_speed has switched to 0
(while it wasn't 0 beforehand).

The only way to recover is to restart the application.

We are using a XL710 NIC within an LXC container.

Would anybody know what could cause this behaviour?

Many thanks.