From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas.monjalon@6wind.com> Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48]) by dpdk.org (Postfix) with ESMTP id 79D482BAC for <dev@dpdk.org>; Mon, 21 Nov 2016 10:40:52 +0100 (CET) Received: by mail-wm0-f48.google.com with SMTP id c184so19758747wmd.0 for <dev@dpdk.org>; Mon, 21 Nov 2016 01:40:52 -0800 (PST) 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=dU6JzJjDXGHJ8lcySMvXEddPpyIkXtKNEuKHPQfw87c=; b=1XyG7UK2SL4NzCtuQas9+nD0rNoIf235pwfQmct6RIe4S+ekBf9BOG6URycqsiBPt3 93JZVK4sQK+XPOVk4Cr445x04D8lX8h3yg+Zm4TEdjFTCh7F9l2LLxrkR2cWz67lu/PV RMz3dWzetzeQwGzWt7CwvUyxCI+JBB7BvqxCMI9UETjHs2+BRvix4qtQwHb+sUyGX16v j6IHiQnBmrHwOsm2rsbQej4oVT0miveMh6yvOSjqn5bp5ovwbsjkZGre/eo6/YKaoRF4 WuJvhUfajh4vyVpZyf1I7FYaq16x56e9OXHAoYaN80fyLM/td+woOKyGBpXL0qvzUMIN a/TQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=dU6JzJjDXGHJ8lcySMvXEddPpyIkXtKNEuKHPQfw87c=; b=LT1Cssb7ihFqRY9UIt7AQaoB5LLScF1RVuYtLNJUIfwa9rbhRehjA2c/nvSvyyi+Q0 96B/Nw3zWC18PPJ99Ylsc3v9CmJZbAaH89RdE15f6XuWr0ia6CV1Ork13LUA1XY46ytR nV3/ipWiKEz0NepS/HXCIkgJcRuPqvYleXiKaI1cpm7WsnDpikIpPPVfTjWLyDVhZUZg STnwelp4WY6N15QwCREaOgLGlVBoafNtY0pqnFDQ6EZcN8dVRchQ0JiX/GqVGJl6/D0n 66eE3RkM5N6l2HpMZgPQrpTY+poxr6khrky9jg6lqRlEAFIBByS/CQJZ9WyCitYbQOYM quIw== X-Gm-Message-State: AKaTC03kkxZt1t/r7WM5RP1qAv2ftre69BstTCuyg+Y09oQqb/niRkAYa6Aie6G6+eUTkmOA X-Received: by 10.28.66.7 with SMTP id p7mr14439056wma.64.1479721252135; Mon, 21 Nov 2016 01:40:52 -0800 (PST) Received: from xps13.localnet (183.20.90.92.rev.sfr.net. [92.90.20.183]) by smtp.gmail.com with ESMTPSA id f126sm18391785wme.22.2016.11.21.01.40.51 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 21 Nov 2016 01:40:51 -0800 (PST) From: Thomas Monjalon <thomas.monjalon@6wind.com> To: Jerin Jacob <jerin.jacob@caviumnetworks.com>, Bruce Richardson <bruce.richardson@intel.com> Cc: dev@dpdk.org, harry.van.haaren@intel.com, hemant.agrawal@nxp.com, gage.eads@intel.com Date: Mon, 21 Nov 2016 10:40:50 +0100 Message-ID: <16834486.NTSXs6S7QZ@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <20161118192715.GA8674@localhost.localdomain> References: <1479447902-3700-1-git-send-email-jerin.jacob@caviumnetworks.com> <20161118160428.GA123692@bricha3-MOBL3.ger.corp.intel.com> <20161118192715.GA8674@localhost.localdomain> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 0/4] libeventdev API and northbound implementation X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK <dev.dpdk.org> List-Unsubscribe: <http://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: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Mon, 21 Nov 2016 09:40:52 -0000 2016-11-19 00:57, Jerin Jacob: > On Fri, Nov 18, 2016 at 04:04:29PM +0000, Bruce Richardson wrote: > > On Fri, Nov 18, 2016 at 03:25:18PM +0000, Bruce Richardson wrote: > > > On Fri, Nov 18, 2016 at 11:14:58AM +0530, Jerin Jacob wrote: > > > > Possible next steps: > > > > 1) Review this patch set > > > > 2) Integrate Intel's SW driver[http://dpdk.org/dev/patchwork/patch/17049/] > > > > 3) Review proposed examples/eventdev_pipeline application[http://dpdk.org/dev/patchwork/patch/17053/] > > > > 4) Review proposed functional tests[http://dpdk.org/dev/patchwork/patch/17051/] > > > > 5) Cavium's HW based eventdev driver > > > > > > > > I am planning to work on (3),(4) and (5) > > > > > > > Thanks Jerin, > > > > > > we'll review and get back to you with any comments or feedback (1), and > > > obviously start working on item (2) also! :-) > > > > > > I'm also wonder whether we should have a staging tree for this work to > > > make interaction between us easier. Although this may not be > > > finalised enough for 17.02 release, do you think having an > > > dpdk-eventdev-next tree would be a help? My thinking is that once we get > > > the eventdev library itself in reasonable shape following our review, we > > > could commit that and make any changes thereafter as new patches, rather > > > than constantly respinning the same set. It also gives us a clean git > > > tree to base the respective driver implementations on from our two sides. > > > > > > Thomas, any thoughts here on your end - or from anyone else? > > I was thinking more or less along the same lines. To avoid re-spinning the > same set, it is better to have libeventdev library mark as EXPERIMENTAL > and commit it somewhere on dpdk-eventdev-next or main tree > > I think, EXPERIMENTAL status can be changed only when > - At least two event drivers available > - Functional test applications fine with at least two drivers > - Portable example application to showcase the features of the library > - eventdev integration with another dpdk subsystem such as ethdev Are you asking for a temporary tree? If yes, please tell its name and its committers, it will be done.