From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by dpdk.space (Postfix) with ESMTP id DAF4FA0679
	for <public@inbox.dpdk.org>; Thu,  4 Apr 2019 21:29:37 +0200 (CEST)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id 7EDA17D4A;
	Thu,  4 Apr 2019 21:29:36 +0200 (CEST)
Received: from mail.lysator.liu.se (mail.lysator.liu.se [130.236.254.3])
 by dpdk.org (Postfix) with ESMTP id B345C5323
 for <dev@dpdk.org>; Thu,  4 Apr 2019 21:29:34 +0200 (CEST)
Received: from mail.lysator.liu.se (localhost [127.0.0.1])
 by mail.lysator.liu.se (Postfix) with ESMTP id 56AD240010
 for <dev@dpdk.org>; Thu,  4 Apr 2019 21:29:34 +0200 (CEST)
Received: by mail.lysator.liu.se (Postfix, from userid 1004)
 id 446E04000E; Thu,  4 Apr 2019 21:29:34 +0200 (CEST)
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on
 bernadotte.lysator.liu.se
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 required=5.0 tests=ALL_TRUSTED,AWL
 autolearn=disabled version=3.4.1
X-Spam-Score: -0.9
Received: from [192.168.1.59] (host-90-232-144-184.mobileonline.telia.com
 [90.232.144.184])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mail.lysator.liu.se (Postfix) with ESMTPSA id 1473340009;
 Thu,  4 Apr 2019 21:29:32 +0200 (CEST)
To: Venky Venkatesh <vvenkatesh@paloaltonetworks.com>,
 "dev@dpdk.org" <dev@dpdk.org>
References: <3353B035-E890-4753-8863-5647DFE61E23@paloaltonetworks.com>
 <8510f66d-a63e-4ef9-44e1-071758fec6fd@ericsson.com>
 <3B32DEF7-8563-4BB5-BB01-0BFE29277B37@paloaltonetworks.com>
 <2fd8bee9-a375-95b7-eb96-eef8b59e531d@ericsson.com>
 <83449720-1B93-4C96-8CF0-7F5753D1F0AA@paloaltonetworks.com>
 <7790bc0b-8c70-fa82-8d34-ba25dbaf226e@ericsson.com>
 <0C690BD4-CB1F-4556-B225-B753670B9E1F@paloaltonetworks.com>
From: =?UTF-8?Q?Mattias_R=c3=b6nnblom?= <mattias.ronnblom@ericsson.com>
Message-ID: <e37fea3f-7c97-2e6a-4365-eb99fe334eb1@ericsson.com>
Date: Thu, 4 Apr 2019 21:29:32 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <0C690BD4-CB1F-4556-B225-B753670B9E1F@paloaltonetworks.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: Re: [dpdk-dev] DSW eventdev is getting "stuck"?
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>
Message-ID: <20190404192932.s0Di5mcj_TeLvWs6IoM5WtX_8Rrn2dc0yQFNUDFC8yw@z>

On 2019-04-04 20:13, Venky Venkatesh wrote:
> On a side note on the design, suppose you have 1 massive flow in terms of work per packet and is "long" lived. Then 1 core would be super busy while others would be idle. Then would it constantly consider migrating that flow since the busy-ness of the core would be above a threshold while others are idle? Again (after migrating) to figure out that the new core is super busy while others are idle and so on ...? A sort of thrashing effect.
> 

When a port considers migration (to reduce its load), it consults the 
last 128 seen events dequeued on that port. If all those events 
originate from the same flow, no flow will be migrated.