From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <vsnv83@gmail.com>
Received: from mail-io0-f193.google.com (mail-io0-f193.google.com
 [209.85.223.193]) by dpdk.org (Postfix) with ESMTP id 5D36868A5
 for <users@dpdk.org>; Wed, 30 Dec 2015 05:58:22 +0100 (CET)
Received: by mail-io0-f193.google.com with SMTP id o67so31502189iof.2
 for <users@dpdk.org>; Tue, 29 Dec 2015 20:58:22 -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
 :cc:content-type;
 bh=dKyRGIbqijduM2JM9O2RVXdyHb0IO21BEARNR74SCHk=;
 b=HE5hGmNN8N2hOGx2xvEd/WDDBP7yXKP+9Vwi5aNm0ZEoL7PQVkP9XA5G3pzgR+2Prn
 zYY+GGTdqYxCWlTQRQJz82RApX2tN5FnWxiAZcvy00lB6OyC2g21evycV3nUn+rGFKo9
 C87UfkAFNb8kAHhyBrWA4nepFuRLZOr0unKGRcC0V5mq9IsmYeDDk3kzTXOhq06sTMeX
 szrKdm3H+XiyZY2pWDa+n1Onj2aePpC67oV1SketE5qKogoRawhRFDDhuqkLP53GdUeL
 l65NSljOWhmKOZfPhkqs1zb5cM16Ib9uGR5GfFOe7rRaAbVNiVpL9HYKA1P72dcpuNGp
 khxw==
MIME-Version: 1.0
X-Received: by 10.107.129.91 with SMTP id c88mr59527158iod.12.1451451501867;
 Tue, 29 Dec 2015 20:58:21 -0800 (PST)
Received: by 10.36.18.131 with HTTP; Tue, 29 Dec 2015 20:58:21 -0800 (PST)
In-Reply-To: <54CBAA185211B4429112C315DA58FF6DD9C232@IRSMSX103.ger.corp.intel.com>
References: <CACDuqmkyotw9tUrOsRJOEXXoK_TaWxo9O3fhtTDc-mG=0VKiEw@mail.gmail.com>
 <54CBAA185211B4429112C315DA58FF6DD9C232@IRSMSX103.ger.corp.intel.com>
Date: Tue, 29 Dec 2015 20:58:21 -0800
Message-ID: <CACDuqmk_i_pLmiUQXSnkhV5UD9j_tmH+qqpe8NPb-7cTwoi3Cg@mail.gmail.com>
From: Vijay S <vsnv83@gmail.com>
To: "Singh, Jasvinder" <jasvinder.singh@intel.com>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Test Pipeline application - lockup
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: usage discussions <users.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Dec 2015 04:58:22 -0000

Hi Jasvinder,

On Tue, Dec 29, 2015 at 3:42 AM, Singh, Jasvinder <jasvinder.singh@intel.com
> wrote:

> Hi Vijay,
>
> >
> > I am running the test pipeline application using extendible bucket hash
> table
> > with 16 byte key size. I have made changes to the test pipeline
> application
> > such that for EVERY port instance there are 3 cores: Rx Core, Worker Core
> > and Tx Core instead of ALL ports mapping to a single Rx/Tx Core like in
> the
> > original implementation. This is being done to try and increase the
> overall
> > throughput of the application.
> >
> > In the app_main_loop_worker_pipeline_hash function, I am instantiating a
> > new pipeline instance for each port and stitching the rings_rx and
> rings_tx
> > accordingly. With these changes I am able to get a throughput of ~13Mpps
> on
> > one 10G port. But, when I send a high rate traffic (13Mpps each) from
> BOTH
> > the ports simultaneously, the traffic stops completely. Stopping the
> > restarting traffic doesn't seem to be helping. It almost looks like the
> pipeline
> > is locked up and not seeing any packets in the Rx rings.
> > Has anyone encountered this before ? Any idea how to debug/what could be
> > going wrong ? Appreciate your help !
>
>
> In pipeline Core, have you created separate table for each pipeline
> instance? Each pipeline instance should have input port, table and output
> port configured and linked properly to make passage for the packets.


Moving to multi-consumer ring apis and allocating rx mbuf per port fixed
the lockup issue. I am able to receive packets on all the ports without any
lockup. Thanks for your help.

Regards,
Vijay