From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by dpdk.org (Postfix) with ESMTP id 0E5795B36 for ; Tue, 9 Apr 2019 22:25:34 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 1D00B31E; Tue, 9 Apr 2019 16:25:33 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 09 Apr 2019 16:25:33 -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=0GJR/cIfbLUppJuheo0eK4nqozx0dF3JPVIUi+fXFxM=; b=Dn4ImdZ0h7cJ x8WIz4VuS7mMCQNKBdst1g0LJQUsNQT+C8KgU3zka2bfZ3rqq0f0vo+CUqZZEZvg Dr9Bziqm8cvGZTxHgMnetIcRmYnn2fys25PkMypwera/Sua1Tq02I+lZoVomAd4+ eF7M6d7z33gVM7eXUW5nDK8qbvbfq44= 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=0GJR/cIfbLUppJuheo0eK4nqozx0dF3JPVIUi+fXF xM=; b=l361labdSzsCj4yxSz8cROG+sTUnegVP8y0kkknUSZQauLTc2hKz9AA3T VyHUHzw4RNJSl1f/eSwCNKViln65R0ICByQSuDj6V1RRNM70XCPXR4uoipE2YQj2 QuNnT611+fgGhHIEAfr/dv3ooXKyO8Jg60X/pZpDReB8qbgQ724O1T+7WS8WFmr+ wwIo+7YLNPtXKTsWDfRKu8wXfIZTU1iPtItGMPhsaPMiQeLVW7UlliXJCuLSXWGr 6WSg8Q4cO2NnD5LSAg7bwUVmGenVD5v2HuIusG1zYx8nq3AJN/Omw06jSMx9C3na dnwWywn3BTc5Xyg1nOzR19qSI6WNA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudehgdduhedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffkjghfggfgtgesthfure dttddtvdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshes mhhonhhjrghlohhnrdhnvghtqeenucfkphepjeejrddufeegrddvtdefrddukeegnecurf grrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtnecu vehluhhsthgvrhfuihiivgeptd 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 67EA7E4122; Tue, 9 Apr 2019 16:25:31 -0400 (EDT) From: Thomas Monjalon To: vivkong@ca.ibm.com Cc: dev@dpdk.org Date: Tue, 09 Apr 2019 22:25:30 +0200 Message-ID: <1653640.BMqFjXm9Gv@xps> In-Reply-To: <20190409190630.31975-1-vivkong@ca.ibm.com> References: <20190409190630.31975-1-vivkong@ca.ibm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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: , X-List-Received-Date: Tue, 09 Apr 2019 20:25:34 -0000 09/04/2019 21:06, Vivian Kong: > To build and run DPDK on Linux on IBM Z (s390x), big endian support > is added and s390x vector intrinics are used in the implementation > of DPDK libraries. > > I appreciate your feedback. I understand you worked on it during some time and you reveal it just now. I must say thank you for the work. It would have been better to notify the community in advance so we would have discussed about the need for this work before you start. First question: What is the use case of DPDK on s390x? Second question: How is it tested? Do you have any CI? Third question: Do you have time to dedicate to DPDK? If yes, why not helping with IBM Power? The reason for this last question is that the support for IBM Power is still beta. I feel unconfortable merging one more IBM arch while the first one does not receive enough support and testing. I think running a CI for IBM Power would be a good first step. 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 A62B8A0096 for ; Tue, 9 Apr 2019 22:25:36 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id EF5405B38; Tue, 9 Apr 2019 22:25:35 +0200 (CEST) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by dpdk.org (Postfix) with ESMTP id 0E5795B36 for ; Tue, 9 Apr 2019 22:25:34 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 1D00B31E; Tue, 9 Apr 2019 16:25:33 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 09 Apr 2019 16:25:33 -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=0GJR/cIfbLUppJuheo0eK4nqozx0dF3JPVIUi+fXFxM=; b=Dn4ImdZ0h7cJ x8WIz4VuS7mMCQNKBdst1g0LJQUsNQT+C8KgU3zka2bfZ3rqq0f0vo+CUqZZEZvg Dr9Bziqm8cvGZTxHgMnetIcRmYnn2fys25PkMypwera/Sua1Tq02I+lZoVomAd4+ eF7M6d7z33gVM7eXUW5nDK8qbvbfq44= 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=0GJR/cIfbLUppJuheo0eK4nqozx0dF3JPVIUi+fXF xM=; b=l361labdSzsCj4yxSz8cROG+sTUnegVP8y0kkknUSZQauLTc2hKz9AA3T VyHUHzw4RNJSl1f/eSwCNKViln65R0ICByQSuDj6V1RRNM70XCPXR4uoipE2YQj2 QuNnT611+fgGhHIEAfr/dv3ooXKyO8Jg60X/pZpDReB8qbgQ724O1T+7WS8WFmr+ wwIo+7YLNPtXKTsWDfRKu8wXfIZTU1iPtItGMPhsaPMiQeLVW7UlliXJCuLSXWGr 6WSg8Q4cO2NnD5LSAg7bwUVmGenVD5v2HuIusG1zYx8nq3AJN/Omw06jSMx9C3na dnwWywn3BTc5Xyg1nOzR19qSI6WNA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudehgdduhedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffkjghfggfgtgesthfure dttddtvdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshes mhhonhhjrghlohhnrdhnvghtqeenucfkphepjeejrddufeegrddvtdefrddukeegnecurf grrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtnecu vehluhhsthgvrhfuihiivgeptd 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 67EA7E4122; Tue, 9 Apr 2019 16:25:31 -0400 (EDT) From: Thomas Monjalon To: vivkong@ca.ibm.com Cc: dev@dpdk.org Date: Tue, 09 Apr 2019 22:25:30 +0200 Message-ID: <1653640.BMqFjXm9Gv@xps> In-Reply-To: <20190409190630.31975-1-vivkong@ca.ibm.com> References: <20190409190630.31975-1-vivkong@ca.ibm.com> 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: <20190409202530.tkVw2cRx2FUXD_VxJDe4SK16OHzewLQaRr_eUIWFEw8@z> 09/04/2019 21:06, Vivian Kong: > To build and run DPDK on Linux on IBM Z (s390x), big endian support > is added and s390x vector intrinics are used in the implementation > of DPDK libraries. > > I appreciate your feedback. I understand you worked on it during some time and you reveal it just now. I must say thank you for the work. It would have been better to notify the community in advance so we would have discussed about the need for this work before you start. First question: What is the use case of DPDK on s390x? Second question: How is it tested? Do you have any CI? Third question: Do you have time to dedicate to DPDK? If yes, why not helping with IBM Power? The reason for this last question is that the support for IBM Power is still beta. I feel unconfortable merging one more IBM arch while the first one does not receive enough support and testing. I think running a CI for IBM Power would be a good first step.