From mboxrd@z Thu Jan  1 00:00:00 1970
From: Patrik Andersson R <patrik.r.andersson@ericsson.com>
Subject: Re: [RFC] vhost user: add error handling for fd > 1023
Date: Mon, 11 Apr 2016 08:06:06 +0200
Message-ID: <570B3ECE.3050905@ericsson.com>
References: <1458292380-9258-1-git-send-email-patrik.r.andersson@ericsson.com>
 <C37D651A908B024F974696C65296B57B4C69D6C7@SHSMSX101.ccr.corp.intel.com>
 <570379F9.6020306@ericsson.com>
 <CAATJJ0LTPKe6hbnWM-noXDbCJ0Y2H6SErg7N8UL1vWuLC1qqLg@mail.gmail.com>
 <C37D651A908B024F974696C65296B57B4C6D90F2@SHSMSX101.ccr.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "dev@dpdk.org" <dev@dpdk.org>, Thomas Monjalon
 <thomas.monjalon@6wind.com>, "Ananyev, Konstantin"
 <konstantin.ananyev@intel.com>, Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: "Xie, Huawei" <huawei.xie@intel.com>, Christian Ehrhardt
 <christian.ehrhardt@canonical.com>, Daniele Di Proietto
 <diproiettod@vmware.com>
Return-path: <dev-bounces@dpdk.org>
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58])
 by dpdk.org (Postfix) with ESMTP id 7D1522E41
 for <dev@dpdk.org>; Mon, 11 Apr 2016 08:06:48 +0200 (CEST)
In-Reply-To: <C37D651A908B024F974696C65296B57B4C6D90F2@SHSMSX101.ccr.corp.intel.com>
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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

I fully agree with this course of action.

Thank you,

Patrik


On 04/08/2016 08:47 AM, Xie, Huawei wrote:
> On 4/7/2016 10:52 PM, Christian Ehrhardt wrote:
>> I totally agree to that there is no deterministic rule what to expect.
>> The only rule is that #fd certainly always is > #vhost_user devices.
>> In various setup variants I've crossed fd 1024 anywhere between 475
>> and 970 vhost_user ports.
>>
>> Once the discussion continues and we have an updates version of the
>> patch with some more agreement I hope I can help to test it.
> Thanks. Let us first temporarily fix this problem for robustness, then
> we consider whether upgrade to (e)poll.
> Will check the patch in detail later. Basically it should work but need
> check whether we need extra fixes elsewhere.