From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <abelyako@gmail.com>
Received: from mail-vc0-f171.google.com (mail-vc0-f171.google.com
 [209.85.220.171]) by dpdk.org (Postfix) with ESMTP id DC30F5B2D
 for <dev@dpdk.org>; Tue, 27 Jan 2015 08:51:35 +0100 (CET)
Received: by mail-vc0-f171.google.com with SMTP id hq11so4238060vcb.2
 for <dev@dpdk.org>; Mon, 26 Jan 2015 23:51:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=qhP679OlbefNEVhswuwT8bi8QIDx40I6SLvsIXyLooI=;
 b=IMPEYQoXR5xiH0PK6EDYflgT3RCCLwrVfBYx6LOx5XoII9FxB6T5TjQFkROnj7qDJW
 E0jf8ITkg5pSWyyeyE+FFvPjaY8Vs6pDb9udKHNrJQ45wmD2luOaoP95sL5WqZZJEqqd
 4zcDdF7AqO0XJ7nXjvSDyJX1r22ADizvpaSq6QMwBFpvJMZ/YW1u8WMTS9JcYPzxFZrU
 5sA2AEKj1JWRUZ0ss9cSJpMQ11g3NGhUHisDChxfgcAmG4WXqw5zYG0AtLwgSfj+yXLM
 44nd8zZNoNkYikEGjWPOKlgV8QnJ7z3fQvRrTetijAzYlnku1/ijBOmJSd766ha0MPpW
 9iBw==
MIME-Version: 1.0
X-Received: by 10.220.98.136 with SMTP id q8mr8531vcn.4.1422345095392; Mon, 26
 Jan 2015 23:51:35 -0800 (PST)
Received: by 10.52.116.105 with HTTP; Mon, 26 Jan 2015 23:51:35 -0800 (PST)
In-Reply-To: <CAAQJX_QN+HWS7k+MMw+NC3UnSKcdr-B=L1nLdOCh1br5eiYD+A@mail.gmail.com>
References: <CAAQJX_Q_eMAG5Raj9yeeg_veGyZVd63A9MWJpq8jYLTOZBonzA@mail.gmail.com>
 <20150126170811.106aa793@uryu.home.lan>
 <CAAQJX_QN+HWS7k+MMw+NC3UnSKcdr-B=L1nLdOCh1br5eiYD+A@mail.gmail.com>
Date: Tue, 27 Jan 2015 10:51:35 +0300
Message-ID: <CAAQJX_RxJZQFqc4biWBNZgbD5HuW=Y9073tV9Tp8UE3A5Ku9Ug@mail.gmail.com>
From: Alexander Belyakov <abelyako@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
 "dev@dpdk.org" <dev@dpdk.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-dev] Fwd:  DPDK testpmd forwarding performace degradation
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jan 2015 07:51:38 -0000

Hello,

On Mon, Jan 26, 2015 at 8:08 PM, Stephen Hemminger <
stephen@networkplumber.org> wrote:

> On Mon, 26 Jan 2015 13:17:48 +0300
> Alexander Belyakov <abelyako@gmail.com> wrote:
>
> > Hello,
> >
> > recently I have found a case of significant performance degradation for
> our
> > application (built on top of DPDK, of course). Surprisingly, similar
> issue
> > is easily reproduced with default testpmd.
> >
> > To show the case we need simple IPv4 UDP flood with variable UDP payload
> > size. Saying "packet length" below I mean: Eth header length (14 bytes) +
> > IPv4 header length (20 bytes) + UPD header length (8 bytes) + UDP payload
> > length (variable) + CRC (4 bytes). Source IP addresses and ports are
> selected
> > randomly for each packet.
> >
> > I have used DPDK with revisions 1.6.0r2 and 1.7.1. Both show the same
> issue.
> >
> > Follow "Quick start" guide (http://dpdk.org/doc/quick-start) to build
> and
> > run testpmd. Enable testpmd forwarding ("start" command).
> >
> > Table below shows measured forwarding performance depending on packet
> > length:
> >
> > No. -- UDP payload length (bytes) -- Packet length (bytes) -- Forwarding
> > performance (Mpps) -- Expected theoretical performance (Mpps)
>
> Did you try using git bisect to identify the problem.
>

I believe dpdk-1.6.0r2 is the first release with bypass adapter (device id
155d) support and it already has the issue. So it seems I have no "good"
point.

Alexander