From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f181.google.com (mail-wr0-f181.google.com [209.85.128.181]) by dpdk.org (Postfix) with ESMTP id 00DDDFA44 for ; Thu, 30 Mar 2017 15:52:24 +0200 (CEST) Received: by mail-wr0-f181.google.com with SMTP id l43so62956532wre.1 for ; Thu, 30 Mar 2017 06:52:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=jV3gElf7uFGW8pOJILHBNZxddcwLsF36DHDbWkFwdv4=; b=i6sT4hHNaFiokYp/4s5WPkTFkP791vXL79FoHPKEdAtf36Vblu+cgj01AaL1Bk9Vt2 WIo0eO8mSs8LK43EgopE1tC3IuNh/Y/bR51dhENj17PC0wuUMvzHWp9C0BVJwB5KQmjv HbpChXZ1UNg76YgRtSUNCX35TS0/XEFMch3lMuwRf5PhYneZc97U+46bATl6+6G1hSwc QV/rQiX2ONYnh1isGOnVUA3DVJsfPEbEYYsOyNmtkapYqRQhFXhwxtsPkv7SI/cQWTLu cQyim8QMtmkdTXDCK+qsihTuR+RcQ/psjMukGRZiCyDIiA6urn+fSXvvbe8FZyTv5wRX b04g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=jV3gElf7uFGW8pOJILHBNZxddcwLsF36DHDbWkFwdv4=; b=Q07/zisYou0Y0pPXGCGTZ6uKiyLUAtrM3UK+hpCY7g6F5oPtzUui1T9zWX88Hgpx13 +wxZ41pbdAuKm1Ib9t8nNlfv9ZUQy9Sd3O0+6N2+RAO228b+RpkoOY+8OQmILKYXgBaR mF1UPnxSOe6P4yINXydjdVGbahk4IYkr3VBh4dwkbssiFbVPZDNA3aEFAy1SOxXS9pm3 pUz0Ue2MGXJb1AgvvCSAgSpLcIErLCaEq4RgEhf5uN/qm66Vye6SAKpyLpFX2W4WkHdw 3zsdjBNYh+CkwaC2zxuHEAQWU2hgyWaw56JcQlj7W+Kn9P5eQ6BxihcLV4BencjZyddB zH9Q== X-Gm-Message-State: AFeK/H1Xl/Sp5tTlywAu77UzdqpIN1/QR8V6qS4YNs30UqoibMUMmcBGd/ayB64RVWFgDOVi X-Received: by 10.223.170.142 with SMTP id h14mr6015979wrc.146.1490881944389; Thu, 30 Mar 2017 06:52:24 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id 191sm3347546wmv.25.2017.03.30.06.52.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Mar 2017 06:52:23 -0700 (PDT) From: Thomas Monjalon To: Hemant Agrawal , shreyansh.jain@nxp.com Cc: Ferruh Yigit , Olivier Matz , dev@dpdk.org Date: Thu, 30 Mar 2017 15:52:22 +0200 Message-ID: <4494502.Baz0AuQ6It@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <31349bbe-0e58-6962-ca41-b231796bd0ba@nxp.com> References: <1489754838-1455-1-git-send-email-hemant.agrawal@nxp.com> <31349bbe-0e58-6962-ca41-b231796bd0ba@nxp.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v1] mempool/dpaa2: add DPAA2 hardware offloaded mempool X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Mar 2017 13:52:25 -0000 2017-03-30 18:20, Hemant Agrawal: > On 3/30/2017 4:59 PM, Ferruh Yigit wrote: > > On 3/28/2017 10:45 AM, Hemant Agrawal wrote: > >> Hi Olivier, > >> > >> On 3/27/2017 10:00 PM, Olivier Matz wrote: > >>> Hi Hemant, > >>> > >>> On Fri, 24 Mar 2017 17:42:46 +0100, Olivier Matz wrote: > >>>>>> From high level, I'm still a little puzzled by the amount of references > >>>>>> to mbuf in a mempool handler code, which should theorically handle any > >>>>>> kind of objects. > >>>>>> > >>>>>> Is it planned to support other kind of objects? > >> > >> We do have plan. However, we also have reservations about using hw > >> mempools for non-packet objects. They generally give advantage when > >> working seamlessly with NICs for rx/tx of packets. > >> > >>>>>> Does this driver passes the mempool autotest? > >> > >> We have tested it internally by manually changing the mempool autotest > >> (mempool name from "stack" to "dpaa2"). we still need to figure out > >> about how to pass the default pool name to autotest. > >> > >>>>>> Can the user be aware of these limitations? > >> > >> That opens a new question, Do We need a documentation for > >> drivers/mempools as well. > >> or, for the time being, we can add this to NXP PMD driver limitations? > >> > >>> > >>> Some more comments. > >>> > >>> I think the mempool model as it is today in DPDK does not match your > >>> driver model. > >>> > >>> For instance, the fact that the hardware is able return the mbuf in the > >>> pool by itself makes me think that the mbuf rework patchset [1] can break > >>> your driver. Especially this patch [2], that expects that m->refcnt=1, > >>> m->nb_segs=1 and m->next=NULL when allocating from a pool. > >>> > >> Yes! we will need to give a small patch, once your patch is applied. > >> > >>> - Can this handler can be used with another driver? > >> > >> NXP mempool is specific to NXP hw only. It is designed to work with with > >> NXP DPAA2 type NICs. There is no limitation in using it with any other > >> PCI NIC connected to NXP Board. We do have tested it with ixgbe (82599) > >> interworking with DPAA2 interfaces. > >> > >>> - Can your driver be used with another mempool handler? > >> No, NXP DPAA2 PMD need NXP mempool only - at least for RX packets. > >> In TX, we can send non-NXP DPAA2 pool packets. (The HW will not free > >> them autonomously, but TX confirm will be required.) > >> > >>> - Is the dpaa driver the only driver that would take advantage of > >>> the mempool handler? Will it work with cloned mbufs? > >>> > >> For now, dpaa driver is the only user. We will be sending cloned-mbuf > >> support patches, once the basic driver is up-stream. > >> > >>> Defining a flag like this in your private code should not be done: > >>> > >>> #define MEMPOOL_F_HW_PKT_POOL (1 << ((sizeof(int) * 8) - 1)) > >>> > >>> Nothing prevents to break it if someone touches the generic flags in > >>> mempool. And hope that no other driver does the same :) > >> > >> Yes! I agree. We need to work with you to improve the overall hw mempool > >> support infrastructure: > >> > >> 1. When transmitting packet, the HW need to differentiate between HW > >> supported pool vs non-HW supported pool packets. (Application may choose > >> to have multiple pools of different type). > >> > >> 2. Option to use a different default mempool when used with virtio-net > >> in VM. You shared your opinion & some possible ways a while back. Now, > >> we are seeing hw mempools actually coming to DPDK. So, We need to > >> re-start this discussion. > >> > >>> > >>> Maybe you can do the same without flag, for instance by checking if > >>> (m->pool == pmd->pool)? > >> > >> This may not work, if more than one instance of hw mempool is in use. > >> > >>> > >>> > >>> I think a new mempool handler should pass the mempool tests, or at least > >>> we should add a new API that would describe the capabilities or something > >>> like that (for instance: support mbuf pool only, support multiprocess). > >>> > >> Let me start working on this asap. we will experiment and send some RFCs. > >> > >>> > >>> To conclude, I'm quite reserved. > >>> Well, all the code is in driver/, meaning it does not pollute the rest. > >> > >> Thanks and understood your concerns. > > > > The discussion is still ongoing for the patch, there are valid concerns, > > the patch is already in the next-net tree, but it may not be merged with > > ongoing discussion. > > > > Btw, since dpaa2 net driver depends this one, we are talking about all > > dpaa2 code (bus, mempool, net). > > > > I think we have following options: > > > > 1) Drop the dpaa2 patches from next-net. > > Work on having an agreement. > > If all parties agreed, target for this release RC2. > > If not, it will slip into next release. > > > > 2) Since these are drivers, scope is limited, > > get PMD as it is for this release, and work for fixes on next release > > This has risk of proper fixes may not happen. > > The dpaa2 hw mempool driver is a a very specific driver and not a > general purpose mempool. It will only be used for dpaa2 pmd. It can only > work on NXP hardware. > > We are already working on suggestion to make sure that mempool_autotest > work and document the mempool limitation in NXP PMD. The patches will be > out shortly. > > The changes in the common/lib area requires a lot of discussions. Some > of the discussion started around the mempool changes for hw support, > never reached a conclusion. They can easily be sequential. > > This driver is not making any changes in the common/lib area. All > changes are confined with the NXP specific driver only. > > If we keep continuing like this, I am afraid that NXP PMD will get stuck > indefinitely. > > > > > > > I am for doing right at first time, so will pick option 1, but also this > > PMD is waiting for some time. So this is a tricky decision, > > Currently, all our work and planning is pending for the PMD to be > integrated in DPDK. Once the basic support is available, we will also > be able to contribute to other areas like eventdev, tm and many other > items. Even our Crypto device patches are pending subject to PMD being > integrated to master. > > > > > Thomas, Hemant, et al, > > > > Can you please comment? Yes it is a tricky decision. It would not be reasonable to postpone this patch to 17.08. However I agree with your position of "doing right at first time". Anyway, the right merge order is to make sure the move of mempool handlers as mempool drivers work fine. We must also merge the mbuf rework (which has not been acknowledged a lot). Then the DPAA2 mempool should be adapted. Can we wait RC2 for a better DPAA2 integration?