From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tetsuya Mukawa <mukawa@igel.co.jp>
Subject: Re: [PATCH v1 0/2] Virtio-net PMD Extension to work on
	host
Date: Wed, 6 Jan 2016 12:57:27 +0900
Message-ID: <568C90A7.9040503@igel.co.jp>
References: <1447930650-26023-2-git-send-email-mukawa@igel.co.jp>
 <1450255049-2263-1-git-send-email-mukawa@igel.co.jp>
 <ED26CBA2FAD1BF48A8719AEF02201E36680E67@SHSMSX103.ccr.corp.intel.com>
 <568117AB.1080605@igel.co.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Cc: "nakajima.yoshihiro@lab.ntt.co.jp" <nakajima.yoshihiro@lab.ntt.co.jp>,
 "mst@redhat.com" <mst@redhat.com>
To: "Tan, Jianfeng" <jianfeng.tan@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-pf0-f177.google.com (mail-pf0-f177.google.com
 [209.85.192.177]) by dpdk.org (Postfix) with ESMTP id 2D8509576
 for <dev@dpdk.org>; Wed,  6 Jan 2016 04:57:26 +0100 (CET)
Received: by mail-pf0-f177.google.com with SMTP id 78so234194020pfw.2
 for <dev@dpdk.org>; Tue, 05 Jan 2016 19:57:26 -0800 (PST)
In-Reply-To: <568117AB.1080605@igel.co.jp>
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 2015/12/28 20:06, Tetsuya Mukawa wrote:
> On 2015/12/24 23:05, Tan, Jianfeng wrote:
>> Hi Tetsuya,
>>
>> After several days' studying your patch, I have some questions as follows:
>>
>> 1. Is physically-contig memory really necessary?
>> This is a too strong requirement IMHO. IVSHMEM doesn't require this in its original meaning. So how do you think of
>> Huawei Xie's idea of using virtual address for address translation? (In addition, virtual address of mem_table could be
>> different in application and QTest, but this can be addressed because SET_MEM_TABLE msg will be intercepted by
>> QTest)
> Hi Jianfeng,
>
> Thanks for your suggestion.
> Huawei's idea may solve contig-mem restriction.
> Let me have time to check it more.

Hi Jianfeng,

I made sure we can remove the restriction with Huawei's idea.
One thing I concern is below.
If we don't use contiguous memory, this PMD will not work with other
'physical' PMDs like e1000 PMD, virtio-net PMD, and etc.
(This is because allocated memory may not  be physically contiguous.)

One of examples is that if we implement like above, in QEMU guest, we
can handle a host NIC directly, but in container, we will not be able to
handle the device.
This will be a restriction for this virtual addressing changing.

Do you know an use case that the user wants to handle 'physical' PMD and
'virtual' virtio-net PMD together?

Tetsuya,