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 624A3A0562; Wed, 14 Apr 2021 15:22:21 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D566C161ADD; Wed, 14 Apr 2021 15:22:20 +0200 (CEST) Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by mails.dpdk.org (Postfix) with ESMTP id 1E50F4013F for ; Wed, 14 Apr 2021 15:22:18 +0200 (CEST) IronPort-SDR: 3dQLtGZI4sE8vS6gb+xDHVuM/G6ZzfOYqBqK/gLt1YaMeV0H9Ay+hvfeGs6QbS8dLtD37JdhBM tV8sM4vHms9A== X-IronPort-AV: E=McAfee;i="6200,9189,9953"; a="255955462" X-IronPort-AV: E=Sophos;i="5.82,222,1613462400"; d="scan'208";a="255955462" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Apr 2021 06:21:58 -0700 IronPort-SDR: jXmld5mPWuZ/7p3FHZpMGIUkt80SSo3OETPI8s0XoYhu5StjzPxLtT0MPsyEcBi3LFdOurBhz3 LJsSM2UZop3A== X-IronPort-AV: E=Sophos;i="5.82,222,1613462400"; d="scan'208";a="424737607" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.7.48]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 14 Apr 2021 06:21:57 -0700 Date: Wed, 14 Apr 2021 14:21:53 +0100 From: Bruce Richardson To: Liang Ma Cc: dev@dpdk.org Message-ID: <20210414131301.GB514@bricha3-MOBL.ger.corp.intel.com> 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: 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 01:52:14PM +0100, Liang Ma wrote: > 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 That should be a warning only, I think and the device should still be available. Is that not the case, or is there a later error? /Bruce