From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 6964CA0562; Wed, 14 Apr 2021 14:52:21 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DFCD9161A70; Wed, 14 Apr 2021 14:52:20 +0200 (CEST) Received: from sender11-of-o51.zoho.eu (sender11-of-o51.zoho.eu [31.186.226.237]) by mails.dpdk.org (Postfix) with ESMTP id 5DC3B4013F for ; Wed, 14 Apr 2021 14:52:19 +0200 (CEST) ARC-Seal: i=1; a=rsa-sha256; t=1618404737; cv=none; d=zohomail.eu; s=zohoarc; b=BW1RJDhtCIFJRtRUCV1vrx2WL6wHWUe+IP8/OtlYP0Vwtqs7oaZ1O/MdMwol2yUgHahQ6RXuGdKrLeQf2ybqovVuKrVQD68wIKV2tqgfVUVDO+ciVX89YD+AbV4aQdGPo6dtJukcdCdYml20JXMLswHqcvGVvXbN6Fqkplkm8hs= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.eu; s=zohoarc; t=1618404737; h=Content-Type:Cc:Date:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:To; bh=KGWn5E4Tfo9mleZOLCClJU5+Fm8EuUjG4UPVhf8jxig=; b=ZZBc642nCdqkURX4oxA9kQxQ8mKiAFJ0brry2Q2tlvs4aMMkkDCLQ0IY2mB4qVWQhv00nFYTi5LXC3uwAVkOCoF0LiFpoTGZstkZrqz0zSThUFktRQqmwMSXglcG8VU2GhK4FerOew5MfCkG+6EN03bSGO+319ncIcg5aPv/ZNA= ARC-Authentication-Results: i=1; mx.zohomail.eu; spf=pass smtp.mailfrom=liangma@liangbit.com; dmarc=pass header.from= header.from= Received: from C02F33EJML85 (153.185.242.35.bc.googleusercontent.com [35.242.185.153]) by mx.zoho.eu with SMTPS id 1618404736558902.0046512945262; Wed, 14 Apr 2021 14:52:16 +0200 (CEST) Date: Wed, 14 Apr 2021 13:52:14 +0100 From: Liang Ma To: Bruce Richardson Cc: dev@dpdk.org Message-ID: References: <20210413182441.GC1185@bricha3-MOBL.ger.corp.intel.com> <20210414104803.GA514@bricha3-MOBL.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210414104803.GA514@bricha3-MOBL.ger.corp.intel.com> X-ZohoMailClient: External Subject: Re: [dpdk-dev] Question about enable CBDMA with ioat PMD ? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Wed, Apr 14, 2021 at 11:48:03AM +0100, Bruce Richardson wrote: > On Wed, Apr 14, 2021 at 11:37:48AM +0100, Liang Ma wrote: > > On Tue, Apr 13, 2021 at 07:24:41PM +0100, Bruce Richardson wrote: > > > On Tue, Apr 13, 2021 at 06:36:38PM +0100, Liang Ma wrote: > > > > Hi Bruce, > > > > I look into current IOAT PMD. I found that looks only support the > > > > latest DSA device which is part of SPR(Please correct me if I'm wrong). > > > > However, there still is lots existing CPU that support previous CBDMA > > > > Intel Quick-DATA technology. SPDK enable those device with uio. > > > > Any hint to enable those CBDMA device with IOAT PMD ? > > > > > > > > > > Hi Liang, > > > > > > These devices are still supported by the driver. In the latest releases the > > > new device support was added but no older device support was removed. > > > Please let us know if you do hit any problems with running it on the CBDMA > > > HW devices, because it should all still be working as before. > > > > > > Regards, > > > /Bruce > > Hi Bruce, > > I hit a problem with CBDMA enabling. > > > > 1. I follow the DPDK IOAT driver Doc, I bind 0000.04.0 device with > > dpdk-devbind.py > > > > 2. I run dpdk-test without any parameter then dpdk-test complain with > > > > EAL: VFIO support initialized > > EAL: 0000:00:04.0 VFIO group is not viable! Not all devices in IOMMU > > group bound to VFIO or unbound > > Requested device 0000:00:04.0 cannot be used > > > > 3. kernel boot parameter include the "intel_iommu=on" > > > > If I still need some extra iommu settings for CBDMA device ? > > > It's an IOMMU limitation, not just for CBDMA but for other devices like > NICs too - you need to ensure all subfunctions on a device are all bound to > the same IOMMU group. So for the CBDMA instance, to use one channel with > vfio, the other channels on the device also need to be bound to vfio, or > else not bound to any driver. If bound to the kernel driver, there will be > IOMMU conflicts as we can't split the channels between kernel and userspace > address spaces. > > /Bruce I bind whole device from 00:04.0 to 00:04.7. ioat PMD complain with "ioat_rawdev_create(): ioat_rawdev_create: Channel appears locked". Any hint? Regards Liang