From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stephen@networkplumber.org>
Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com
 [209.85.192.182]) by dpdk.org (Postfix) with ESMTP id 9C795591A
 for <dev@dpdk.org>; Mon, 26 Jan 2015 18:08:23 +0100 (CET)
Received: by mail-pd0-f182.google.com with SMTP id z10so12900604pdj.13
 for <dev@dpdk.org>; Mon, 26 Jan 2015 09:08:23 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to
 :references:mime-version:content-type:content-transfer-encoding;
 bh=VrhW2KJL125QAVtHE2ZUw2GyGJErHaIE+OCBgIvK8JA=;
 b=Aql2DFAKJuX+igBmgHe5gbrRtcLIa/xDoOxUdkUoNJGaFNIhqAyJk+wo8FnHMslcSB
 Gpv1p34etWxfJMz91S9vRYgguw/E5ngbCLGZiqB8XnEn6366yIc3pBm3lahHRTKdYEeq
 bNXiW/8+a9tIh0PfKof71TVPSoNnEGYrXTMnnglfYjFrh4900ta2X60I5BjyAl0oXYYu
 84rl/Eap/72WN8gb6mebw/rjJgzccevT608V/Kcv5hkQJjogL2n4bYtSHXM7Gv+u1xpc
 DUyJqxm/+cGwqtaJo2gGNLjWUsGeFra0nuwd8UctSKFrZ/XIxnQLDg1vjnywXqPuFKuS
 d3/Q==
X-Gm-Message-State: ALoCoQkJ97uPPbrfYNohGaPI3OqewBjtuD8tNAtuFODjQUnP+xpauyXNxFoWBG3yTanx+7K4phCN
X-Received: by 10.68.238.35 with SMTP id vh3mr36467449pbc.38.1422292102922;
 Mon, 26 Jan 2015 09:08:22 -0800 (PST)
Received: from uryu.home.lan ([144.49.132.22])
 by mx.google.com with ESMTPSA id ej9sm10255937pdb.1.2015.01.26.09.08.20
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Mon, 26 Jan 2015 09:08:22 -0800 (PST)
Date: Mon, 26 Jan 2015 17:08:11 +0000
From: Stephen Hemminger <stephen@networkplumber.org>
To: Alexander Belyakov <abelyako@gmail.com>
Message-ID: <20150126170811.106aa793@uryu.home.lan>
In-Reply-To: <CAAQJX_Q_eMAG5Raj9yeeg_veGyZVd63A9MWJpq8jYLTOZBonzA@mail.gmail.com>
References: <CAAQJX_Q_eMAG5Raj9yeeg_veGyZVd63A9MWJpq8jYLTOZBonzA@mail.gmail.com>
X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] 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: Mon, 26 Jan 2015 17:08:25 -0000

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.