From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id F122EA0096 for ; Wed, 10 Apr 2019 19:43:39 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 6D2C21B39A; Wed, 10 Apr 2019 19:43:39 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id EEAC51B399 for ; Wed, 10 Apr 2019 19:43:37 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 8E75020D89; Wed, 10 Apr 2019 13:43:37 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 10 Apr 2019 13:43:37 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=SLrSKyIa9U8ktzAfCqh3Alk7M0QqhxQWB+0jtWBQvdo=; b=pf6FKs/hgExx U5I3vh2aQeCFhllbuT17/AkhVMPFE5FwuC7YN9A4URdclvKHmGFRr9/KGhdIW7CC xz20w360plMcmMwb2DtJXIeba27TQbl2CeC84AmxIORCv6lU4N16nwabkWrLNJ8l 4CiGx3ccYDTRy65UxzyKOEIfB82KDjE= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=SLrSKyIa9U8ktzAfCqh3Alk7M0QqhxQWB+0jtWBQv do=; b=sbEfMGq3XchXjJ1TuJ27azMllLPdU789HSniFZW8pzMewJ/5Sbu2TCXtP IeqYN3sWNlHDsbm+IqTBfneEeWqO+DOO5XotwZDOsdAcymaZ8F9pQbcSWufqe6Md NfcXM1DnkvwVQ4nUeHACfKG+f+RSgshzdG4Amks97Wav0fXixSx+gmNFioZcLMlx AA61qGIlRzmIc2INxJUeVowF/UfLktT1iGQD2ecQrI004rCbwmow7agDSK+EAP/P 0WmwSD0TCtr6Jck1rZwn4MEcQJlnEYVfqswXIAOaRVnuwenU/if/YB99v2fCpaBz m7Drs0picR5KLnUHP12cXn3Q3AGgQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudejgdduudekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuff homhgrihhnpeguphgukhdrohhrghenucfkphepjeejrddufeegrddvtdefrddukeegnecu rfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtne cuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 889F3E4332; Wed, 10 Apr 2019 13:43:36 -0400 (EDT) From: Thomas Monjalon To: Vivian Kong Cc: dev@dpdk.org Date: Wed, 10 Apr 2019 19:43:34 +0200 Message-ID: <2013805.Te0adFJsA8@xps> In-Reply-To: References: <20190409190630.31975-1-vivkong@ca.ibm.com> <1653640.BMqFjXm9Gv@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [RFC 00/12] introduce s390x architecture 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190410174334.rBo8VzopxjrIKEm1EEsku1MWJbCUM_k5nVMzp4T7cZo@z> 10/04/2019 19:09, Vivian Kong: > Hi Thomas, > > Thanks for your comments. Please see my answers to your questions below. > > > First question: What is the use case of DPDK on s390x? > > IBM would like to use DPDK in our new IBM cloud offering on Z. > > > > > Second question: How is it tested? Do you have any CI? > > We ran the tests by "make tests". We don't have CI set up at the moment > but this is definitely something we are looking into adding. > > > > > Third question: Do you have time to dedicate to DPDK? > > After this initial port, we do plan to keep currency base on need but how > frequent will be determined by usage. > > > > > If yes, why not helping with IBM Power? > > Our work is specific to Z offering, we'll be interested to run CI for Z > also which will help maintaining our currency. > > How is CI set up on the platforms currently supported in DPDK? It looks > like a build gets run after a patch is submitted. Wondering if there are > any documentation on how this is set up? There is no complete documentation, but we should build one. That would be great if you could help while riding this path. Some starting points: https://patches.dpdk.org http://git.dpdk.org/tools/dpdk-ci/ http://mails.dpdk.org/listinfo/ci Please help with IBM Power CI at the same time. I would like to see some progress on this front before integrating a new IBM CPU.