From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luke Gorrie Subject: Possible bug in mlx5_tx_burst_mpw? Date: Wed, 14 Sep 2016 15:24:07 +0200 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 To: "dev@dpdk.org" Return-path: Received: from mail-wm0-f44.google.com (mail-wm0-f44.google.com [74.125.82.44]) by dpdk.org (Postfix) with ESMTP id B53D98D4D for ; Wed, 14 Sep 2016 15:24:08 +0200 (CEST) Received: by mail-wm0-f44.google.com with SMTP id i130so48465878wmf.0 for ; Wed, 14 Sep 2016 06:24:08 -0700 (PDT) List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Howdy, Just noticed a line of code that struck me as odd and so I am writing just in case it is a bug: http://dpdk.org/browse/dpdk/tree/drivers/net/mlx5/mlx5_rxtx.c#n1014 Specifically the check "(mpw.length != length)" in mlx_tx_burst_mpw() looks like a descriptor-format optimization for the special case where consecutive packets on the wire are exactly the same size. This would strike me as peculiar. Just wanted to check, is that interpretation correct and if so then is this intentional? Cheers, -Luke