From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: [PATCH v6 1/4] eal/vfio: add multiple container
	support
Date: Thu, 12 Apr 2018 17:24:25 +0100
Message-ID: <36187714-3454-38ee-1836-204790d93e10@intel.com>
References: <20180405180701.16853-4-xiao.w.wang@intel.com>
 <20180412071956.66178-1-xiao.w.wang@intel.com>
 <20180412071956.66178-2-xiao.w.wang@intel.com>
 <974c9cd0-87c4-6ab1-0787-9278a7379fda@intel.com>
 <B7F2E978279D1D49A3034B7786DACF406F88D1F2@SHSMSX101.ccr.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "dev@dpdk.org" <dev@dpdk.org>,
 "maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
 "Wang, Zhihong" <zhihong.wang@intel.com>, "Bie, Tiwei"
 <tiwei.bie@intel.com>, "Tan, Jianfeng" <jianfeng.tan@intel.com>,
 "Liang, Cunming" <cunming.liang@intel.com>, "Daly, Dan"
 <dan.daly@intel.com>, "thomas@monjalon.net" <thomas@monjalon.net>,
 "gaetan.rivet@6wind.com" <gaetan.rivet@6wind.com>,
 "hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
 "Chen, Junjie J" <junjie.j.chen@intel.com>
To: "Wang, Xiao W" <xiao.w.wang@intel.com>,
 "Yigit, Ferruh" <ferruh.yigit@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mga18.intel.com (mga18.intel.com [134.134.136.126])
 by dpdk.org (Postfix) with ESMTP id 76D601C153
 for <dev@dpdk.org>; Thu, 12 Apr 2018 18:24:36 +0200 (CEST)
In-Reply-To: <B7F2E978279D1D49A3034B7786DACF406F88D1F2@SHSMSX101.ccr.corp.intel.com>
Content-Language: en-US
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://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: <https://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 12-Apr-18 5:07 PM, Wang, Xiao W wrote:
> Hi Anatoly,
> 

<...>

>>
>> Also, why providing DMA type? There's already a VFIO type pointer in
>> vfio_config - you can set this pointer for every new created container,
>> so the user wouldn't have to care about IOMMU type. Is it not possible
>> to figure out DMA type from within EAL VFIO? If not, maybe provide an
>> API to do so, e.g. rte_vfio_container_set_dma_type()?
> 
> It's possible, EAL VFIO should be able to figure out a container's DMA type.

You probably won't be able to do it until you add a group into the 
container, so probably best place to do it would be on group_bind?

-- 
Thanks,
Anatoly