From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yk0-f174.google.com (mail-yk0-f174.google.com [209.85.160.174]) by dpdk.org (Postfix) with ESMTP id B14B28E86 for ; Tue, 3 Nov 2015 23:25:54 +0100 (CET) Received: by ykba4 with SMTP id a4so41511925ykb.3 for ; Tue, 03 Nov 2015 14:25:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=callistech_com.20150623.gappssmtp.com; s=20150623; h=mime-version:date:message-id:subject:from:to:content-type; bh=0rAGbHPMEuQ2pmRKcTqW3p/eem6YLZ2FBMUpPfGlTD4=; b=gR2JJbpDUfR7YbDgZyBZWuSC67xJvzExCt227/iDixS/OQ2IfNmqx3B1JHoJbxzams +NAUc8TSErGc4v3UFynlNvnJZW4IQ9odppIYeUl2ZBvZubfMskYsyViCry84oqD9APcp XaqUHx5F5KFkIjT7WT9YeAgmeS14yoDwDvZ1Cn7FUrYMSejAOT6Xg3xd1ian3v675+YY zzvSvup149bcc+oHG0War3IU8Hl+L/KVZpTJMWB/Qj8H1l1PK09+G6w9beWvTxEFp71I sW/cG16AQEEqDGcYZs9/OlJLavHu1BrI2Z7tQjrDaLfM84Ukrjhk/OV1iBMXWHq3oK6W 5Ogw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=0rAGbHPMEuQ2pmRKcTqW3p/eem6YLZ2FBMUpPfGlTD4=; b=Vt2UsjN0LRkLZSGcwhkL8Mz46zNI+A7OaCCP/YTG7dQyFQIoNnJaxJS9H//ZiFRxfY YF7VucnFRsvEz80qev/XBhc0T7pGzwPWI4GQBx8Ixx9YwmDej3KUO+1jIDvf9QbGrdfv JkJUDSv5OxUKNWz4S8PfGNC88ltJJcYhAJN2dNZ5EHap6+vg7y/60amKWJUvZmrbpKf2 sXuZ+N3tW1+P2a/NEroMto4XNTK9ryimPHzCNP+GS+2ZzenVdkyTzsp6nxeRxWo/Jd4Q E2TvJlyDkn4R3MbCtrWb1R/tuqAfooWIf2ZTZ0c33wwMnQwQOPeyu3hKhp3l/LSz5Xsc 45tg== X-Gm-Message-State: ALoCoQmW0jOz0psP/gKxNAGs7jAqP1w8EphtQvCjocBTq5WiVspdz7h41UEmhOTpY9i+ZNaj/bAg MIME-Version: 1.0 X-Received: by 10.129.130.6 with SMTP id s6mr22459007ywf.155.1446589554006; Tue, 03 Nov 2015 14:25:54 -0800 (PST) Received: by 10.129.83.134 with HTTP; Tue, 3 Nov 2015 14:25:53 -0800 (PST) Date: Tue, 3 Nov 2015 19:25:53 -0300 Message-ID: From: Ariel Rodriguez To: "dev@dpdk.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] Problem after hours of running rte_eth_rx_burst X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2015 22:25:55 -0000 After several hours (6 hour average) of running a dpdk application , rte_eth_rx_burst suddenly fills only one mbuf with no data, thats is an mbuf with mbuf->pool == NULL && m->buf_physaddr == 0 && m->buf_addr == NULL. Obviosly that breaks our application. (rte_mbuf_sanity_check abort the program) How can we track the source of this kind of mis- behavoir? We are using dpdk 1.6.0r2 and we also use the qos framework api. The nic is 82599ES 10-Gigabit SFI/SFP+ with tapped traffic. The use case is simply, our client is using a traffic tap to divert a copy of around 10gbps of traffic to our appliance. We use a rxtx code similar to the load_balancer example. We read in a pair of rx queue and the use a hash function over the source ip field to deliver the packet in a worker core. Then , when the worker core finishes to process that packet and it is delivery to the tx core. The tx core enqueue the packet to the qos framework, and just a few lines code later dequeue several packet from the qos scheduler. Because we are using a tap to divert a copy of the traffic , we disable the tx code to the phisycal nic, so when we dequeue packets from the qos scheduler wi just drop all of that packets. Of course there is a reason why we use the qos scheduler code without physically transmiting a packet, and is because we just want a few stats about the qos framework behaviour. Any ideas?