From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shreyansh Jain Subject: Re: [PATCH v2 00/40] Introduce NXP DPAA Bus, Mempool and PMD Date: Wed, 5 Jul 2017 10:08:59 +0530 Message-ID: <7a60545f-0853-6db4-342c-575f7d3e93ae@nxp.com> References: <1497591668-3320-1-git-send-email-shreyansh.jain@nxp.com> <1499179471-19145-1-git-send-email-shreyansh.jain@nxp.com> <2228750.hDQQI7liEJ@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Cc: , , To: Thomas Monjalon Return-path: Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0054.outbound.protection.outlook.com [104.47.34.54]) by dpdk.org (Postfix) with ESMTP id 24D1F2A58 for ; Wed, 5 Jul 2017 06:29:56 +0200 (CEST) In-Reply-To: <2228750.hDQQI7liEJ@xps> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hello Thomas, On Wednesday 05 July 2017 05:43 AM, Thomas Monjalon wrote: > Hi Shreyansh, > > 04/07/2017 16:43, Shreyansh Jain: >> This patchset introduces the following: >> 1. DPAA Bus (drivers/bus/dpaa) >> The core of DPAA bus is implemented using 3 main hardware blocks: QMan, >> or Queue Manager; BMan, or Buffer Manager and FMan, or Frame Manager. >> The patches introduce necessary layers to expose the DPAA hardware >> blocks for interfacing with RTE framework. >> >> 2. DPAA Mempool (drivers/mempool/dpaa) >> BMan, or Buffer Manager, block of DPAA features a hardware offloaded >> mempool. These patches add support for a driver to manage the BMan >> block. This driver allows for mempool creation, deletion, buffer >> acquire and release, as per the RTE APIs. >> >> 3. DPAA PMD (drivers/net/dpaa) >> The Poll Mode Driver for DPAA NIC Interfaces. > > There is so much to review in this series! > (and not much reviews) > I hope you were not expecting a quick integration. I understand this. Ferruh has been putting in quite an effort - but yes, other than that, lack of external review. I am just expecting inputs - if there are none, then probably that would be integration point (other than continuous improvements we do internally) or patches might stagnate. But just a random thought off my head (which might help me as a reviewer): How does one review integral/infrastructure related code blocks without a deep insight? ethdev/rxtx are relatively much easier/relevant for reviewers - but not low level blocks. In case of DPAA, that (core routines) is a huge chunks. And, if there are not much reviews (because of lack of interest, or whatever reason), what should an author do (besides gently requesting others, and doing some himself/herself). > > Please could you start checking what checkpatch is saying? > I have seen those - and ignored them for a while. They are related to complex statements defined as macros. Unfortunately, at some of the places, I can't avoid it. Otherwise, there are some which require code-restructuring (deep indentation), which I plan to do shortly. - Shreyansh