From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tetsuya Mukawa <mukawa@igel.co.jp>
Subject: Re: [RFC PATCH 5/5] virtio: Extend virtio-net PMD to
 support container environment
Date: Thu, 28 Jan 2016 15:29:56 +0900
Message-ID: <56A9B564.8000404@igel.co.jp>
References: <1453108389-21006-2-git-send-email-mukawa@igel.co.jp>
 <1453374478-30996-6-git-send-email-mukawa@igel.co.jp>
 <C37D651A908B024F974696C65296B57B4C5B2D0D@SHSMSX101.ccr.corp.intel.com>
 <56A9815F.6040205@igel.co.jp>
 <C37D651A908B024F974696C65296B57B4C5B51A5@SHSMSX101.ccr.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
To: "Xie, Huawei" <huawei.xie@intel.com>, "dev@dpdk.org" <dev@dpdk.org>,
 "yuanhan.liu@linux.intel.com" <yuanhan.liu@linux.intel.com>,
 "Tan, Jianfeng" <jianfeng.tan@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-pa0-f53.google.com (mail-pa0-f53.google.com
 [209.85.220.53]) by dpdk.org (Postfix) with ESMTP id 6F71A9A8D
 for <dev@dpdk.org>; Thu, 28 Jan 2016 07:30:01 +0100 (CET)
Received: by mail-pa0-f53.google.com with SMTP id uo6so18330099pac.1
 for <dev@dpdk.org>; Wed, 27 Jan 2016 22:30:01 -0800 (PST)
In-Reply-To: <C37D651A908B024F974696C65296B57B4C5B51A5@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>

On 2016/01/28 15:15, Xie, Huawei wrote:
> On 1/28/2016 10:48 AM, Tetsuya Mukawa wrote:
>> I measured it, and seems it takes 0.35 seconds in my environment.
>> This will be done only once when the port is initialized. Probably it's
>> not so heady.
> There are 256 x 32 loop of pci scan. That is too long if we dynamically
> start/tear down the container, otherwise it is ok. Some people are
> struggling reducing the VM booting time from seconds to milliseconds to
> compete with container technology. Let us consider if we could optimize
> this.
> For example, QEMU supports specifying bus/dev for a device in its
> commandline, so could we assign fixed bus for virtio-net and ivshm
> device? And for piix3, is it on bus 0/1?
>

OK, I understand the necessity. Let's consider it.
So far, the users doesn't need to specify pci address on QEMU command
line and DPDK vdev option.
But, let's change this, then we can remove this looping.

Probably specifying pci address on vdev option will not be mandatory.
if not specified, just using default value is nice.
I will fix like above in next release.

Tetsuya