* Re: [dpdk-dev] Project Governance and Linux Foundation
@ 2016-10-12 5:44 qin.chunhua
2016-10-12 7:43 ` Thomas Monjalon
0 siblings, 1 reply; 7+ messages in thread
From: qin.chunhua @ 2016-10-12 5:44 UTC (permalink / raw)
To: dev, users, tim.odriscoll
ZTE is supportive of improving the DPDK project governance including
moving the project to the Linux Foundation.
DPDK has been used in lots of ZTE's equipments and solutions such as
BBU,RNC,EPC,vEPC,vBRAS,vCPE,vRouter,vSwitch,and so on for many years.
We have also done some optimization in DPDK. If the DPDK project
governance moves to the Linux Foundation,we think this will promote ZTE
and other companies to contribute in DPDK.
Thanks
Chunhua
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of O'Driscoll, Tim
Sent: Monday, October 10, 2016 4:33 PM
To: dev@dpdk.org; users@dpdk.org
Subject: [dpdk-dev] Project Governance and Linux Foundation
This email is being sent on behalf of: Cavium, Cisco, Intel, NXP & Red
Hat.
Since its creation as an open source project in 2013, DPDK has grown
significantly. The number of DPDK users, contributors, commercial products
that use DPDK and open source projects that depend on it have all
increased consistently over that time. DPDK is now a key ingredient in
networking and NFV, and we need to ensure that the project structure and
governance are appropriate for such a critical project, and that they
facilitate the project's continued growth.
For over a year now we've been discussing moving DPDK to the Linux
Foundation. We believe it's now time to conclude that discussion and make
the move. The benefits of doing this would include:
- The infrastructure for a project like DPDK should not be owned and
controlled by any single company.
- Remove any remaining perception that DPDK is not truly open.
- Allow the project to avail of the infrastructure and services provided
by the Linux Foundation. These include things like: Ability to host
infrastructure for integration and testing (the FD.io CSIT lab is an
example of this - see https://wiki.fd.io/view/CSIT/CSIT_LF_testbed);
Support for legal issues including trademarks and branding, and the
ability to sign agreements on behalf of the project; Ability to pool
resources for events and brand promotion; Safe haven for community IP
resources.
We don't propose to debate the details here. Instead, an open discussion
session on DPDK Project Growth has been included in the agenda for the
DPDK Summit Userspace 2016 event in Dublin. We propose using that session
to agree that the DPDK project will move to the Linux Foundation, and then
to move on to discussing the specifics. Things that we'll need to consider
include:
- Whether DPDK moves to the Linux Foundation as an independent project or
as part of a larger project like FD.io.
- Creation of a project charter similar to those created for FD.io (
https://fd.io/governance/technical-community-charter) and Open vSwitch
(see
http://openvswitch.org/pipermail/discuss/attachments/20160619/5a2df53e/attachment-0001.pdf
).
- Agreement on budget, membership levels etc. A draft budget was created
by the LF during previous discussions (
https://docs.google.com/spreadsheets/d/1-3686Xb_jf4FtxdX8Mus9UwIxUb2vI_ppmJV5GnXcLg/edit#gid=302618256
), but it is possible to adopt an even more lightweight model.
We could look at alternatives to the Linux Foundation, but a) we've been
talking to the LF for over a year now, and b) the preponderance of
networking projects in LF, like ODL, FD.io, and OVS, makes it a natural
destination for DPDK.
As highlighted in previous discussions on this topic, it's important to
stress that the intent is not to make significant changes to the technical
governance and decision making of the project. The project has a strong
set of maintainers and a Technical Board in place already. What's required
is to supplement that with an open governance structure taking advantage
of the services offered by the Linux Foundation.
The purpose of this email is to outline what we want to achieve during
that discussion session in Dublin, and to allow people to consider the
issue and prepare in advance. If people want to comment via email on the
mailing list, that's obviously fine, but we believe that an open and frank
discussion when people meet in person in Dublin is the best way to
progress this.
For reference, below is a brief history of the previous discussions on
this topic:
September 2015:
- A DPDK community call was held to discuss project growth and possible
improvements. This was the first public discussion on possible governance
changes. The agreed next step was to discuss this in more detail at the
2015 DPDK Summit Userspace event Dublin. Minutes of the call are at:
http://dpdk.org/ml/archives/dev/2015-September/024120.html.
October 2015:
- An open discussion session on project governance was held at the 2015
DPDK Summit Userspace event. For technical governance, we agreed to
investigate creating a technical steering committee. For non-technical
governance (including things like event planning, legal and trademark
issues, hosting of the website etc.), we agreed to work with the Linux
Foundation on a proposal for a lightweight governance model for DPDK.
Minutes of the discussion are at:
http://dpdk.org/ml/archives/dev/2015-October/024825.html.
- The proposal for a technical steering committee was subsequently
discussed on the mailing list (
http://dpdk.org/ml/archives/dev/2015-October/026598.html) and agreed,
leading to the creation of the DPDK Technical Board (
http://dpdk.org/dev#board).
December 2015:
- A community call was held to discuss migration to the Linux Foundation.
Mike Dolan (VP of Strategic Programs at The Linux Foundation) gave an
overview of the LF and the services they can provide. We agreed to form a
small sub-team (Dave Neary, Thomas Monjalon, Stephen Hemminger, Tim
O'Driscoll) to work with the LF on a more detailed proposal. Minutes of
the call are at: http://dpdk.org/ml/archives/dev/2015-December/030532.html
.
February 2016:
- A community call was held to discuss the LF budget proposal (see
https://docs.google.com/spreadsheets/d/1-3686Xb_jf4FtxdX8Mus9UwIxUb2vI_ppmJV5GnXcLg/edit#gid=302618256
). We agreed to discuss this further on the dev mailing list due to
limited attendance on the call. Minutes of the call are at:
http://dpdk.org/ml/archives/dev/2016-February/032720.html.
- A request was made on the dev and announce mailing lists too determine
who supported the proposal to move to the Linux Foundation (
http://dpdk.org/ml/archives/dev/2016-February/033192.html). There was
public support from Intel (
http://dpdk.org/ml/archives/dev/2016-February/033297.html) and Brocade (
http://dpdk.org/ml/archives/dev/2016-February/033359.html). 6WIND
requested postponing the move for a few months (
http://dpdk.org/ml/archives/dev/2016-February/033299.html).
- The Fast Data (FD.io) project was established under the Linux Foundation
(
https://fd.io/news/announcement/2016/02/linux-foundation-forms-open-source-effort-advance-io-services
).
June 2016:
- The Open vSwitch project proposed moving to the Linux Foundation (
http://openvswitch.org/pipermail/discuss/2016-June/021761.html).
August 2016:
- The Open vSwitch project moved to the Linux Foundation (
https://www.linuxfoundation.org/announcements/open-vswitch-joins-linux-foundation-open-networking-ecosystem
).
From akhil.goyal@nxp.com Wed Oct 12 07:48:51 2016
Return-Path: <akhil.goyal@nxp.com>
Received: from NAM01-BN3-obe.outbound.protection.outlook.com
(mail-bn3nam01on0052.outbound.protection.outlook.com [104.47.33.52])
by dpdk.org (Postfix) with ESMTP id A87576CCF
for <dev@dpdk.org>; Wed, 12 Oct 2016 07:48:51 +0200 (CEST)
Received: from BN6PR03CA0041.namprd03.prod.outlook.com (10.175.124.27) by
BLUPR03MB326.namprd03.prod.outlook.com (10.141.48.16) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id
15.1.587.13; Wed, 12 Oct 2016 05:48:50 +0000
Received: from BN1BFFO11FD009.protection.gbl (2a01:111:f400:7c10::1:145) by
BN6PR03CA0041.outlook.office365.com (2603:10b6:404:10c::27) with Microsoft
SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.639.5 via Frontend
Transport; Wed, 12 Oct 2016 05:48:50 +0000
Authentication-Results: spf=fail (sender IP is 192.88.168.50)
smtp.mailfrom=nxp.com; nxp.com; dkim=none (message not signed)
header.d=none;nxp.com; dmarc=fail action=none header.from=nxp.com;nxp.com;
dkim=none (message not signed) header.d=none;
Received-SPF: Fail (protection.outlook.com: domain of nxp.com does not
designate 192.88.168.50 as permitted sender) receiver=protection.outlook.com;
client-ip=192.88.168.50; helo=tx30smr01.am.freescale.net;
Received: from tx30smr01.am.freescale.net (192.88.168.50) by
BN1BFFO11FD009.mail.protection.outlook.com (10.58.144.72) with Microsoft SMTP
Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.629.5
via Frontend Transport; Wed, 12 Oct 2016 05:48:47 +0000
Received: from netperf2.ap.freescale.net ([10.232.133.164])
by tx30smr01.am.freescale.net (8.14.3/8.14.0) with ESMTP id u9C5mgHa018413;
Tue, 11 Oct 2016 22:48:43 -0700
From: <akhil.goyal@nxp.com>
To: <arkadiuszx.kusztal@intel.com>, <declan.doherty@intel.com>
CC: <john.griffin@intel.com>, <fiona.trahe@intel.com>,
<deepak.k.jain@intel.com>, <dev@dpdk.org>, Akhil Goyal <akhil.goyal@nxp.com>
Date: Wed, 12 Oct 2016 16:46:29 +0530
Message-ID: <20161012111629.14126-1-akhil.goyal@nxp.com>
X-Mailer: git-send-email 2.9.3
In-Reply-To: <20161007170608.27685-1-akhil.goyal@nxp.com>
References: <20161007170608.27685-1-akhil.goyal@nxp.com>
X-EOPAttributedMessage: 0
X-Matching-Connectors: 131207249300019698;
(91ab9b29-cfa4-454e-5278-08d120cd25b8); ()
X-Forefront-Antispam-Report: CIP:192.88.168.50; IPV:NLI; CTRY:US; EFV:NLI;
SFV:NSPM;
SFS:(10009020)(6009001)(7916002)(2980300002)(1109001)(1110001)(339900001)(199003)(189002)(18543002)(19580395003)(105606002)(76176999)(5003940100001)(50986999)(85426001)(92566002)(47776003)(7846002)(305945005)(8666005)(356003)(19580405001)(8936002)(50226002)(104016004)(11100500001)(77096005)(8676002)(81156014)(81166006)(189998001)(86152002)(87936001)(86362001)(68736007)(97736004)(5001770100001)(5660300001)(626004)(33646002)(48376002)(106466001)(229853001)(1076002)(586003)(4326007)(36756003)(6666003)(2950100002)(2906002)(50466002)(2876002)(7059030);
DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR03MB326; H:tx30smr01.am.freescale.net;
FPR:; SPF:Fail; PTR:InfoDomainNonexistent; A:1; MX:1; LANG:en;
X-Microsoft-Exchange-Diagnostics: 1; BN1BFFO11FD009;
1:gwefd5nHjbtTJY5xThRjKqON/JawIV9o42v86lx+PDyORg6eooSoLJSM3Lif2JOZzB/CfloV2L94vOQSulM7ZDpRymCr9/ofH/4IxE6pem+Q9ckdLswB9fWT7oqkldZmZDi9LU4l1TQxsLXBz1TVcyydIGp0xv/G0jLkm2DcrMVAU5ftMTgXuRTPALPGMUnJ0k3MPV0s8jtq90DzrVII7SOqISVrZoA0AoeSF4nrDbSjmGtuvmCCPD/ifpyVERD9HpKG3EVu81qih+XE6p/CT7edRl54l/oy5wOzFSP6sp5ku1pyFN7xev7zLWLskW49IzI+YvRrzDdrvKD54WW6WQA7v+QctuvjqhGuC6aJo6FpB3bEVX3+6UfPErgG3xeA70J1Ku4CI0XIXAZ/bAkpLGVkVQRvmxsJ2yc+94221VRpnKQ1CsnUP4DAX8rE0GYcPi43tgN5n3GALdfb8yV1MX3dPIzk6It0mxA5L1IPVqOIU+1/A4ea3CurzhiE1itZvnfQqpi6b4rcIQ5B2KfBUdLj3e9GhGX4QW1fY6HdEsiP9UYaR33ubBdPofxWsiQ70rylY7KFNGpc298++H9uH/uS+KOYrFplYnmW2TbdJpuph460dNiXmAxUpVPy7sbqdfJBe0AVRSggfCZghdPuok54fKIdSznQ8U2aLjFXNPOH21Tcc7J/uXU0RsQmAlbNTf/FiIEoWr6C1M7f7/aW27i+5k90SttUQ6RBmE8HmS4hho1ybMLUZnbo3lX3Ab+fLQ8KnQ+cdM/clKVVv+4HHg==
MIME-Version: 1.0
Content-Type: text/plain
X-MS-Office365-Filtering-Correlation-Id: 7c71ee70-b4b2-424a-1730-08d3f26370ee
X-Microsoft-Exchange-Diagnostics: 1; BLUPR03MB326;
2:z6sgUx0/ZR7NuWnxeJOXXh0ZHuTxnksy/ZtNDsgu63z8bn0C3eDDbWVYxgoYIxMaUbFf1DKNg9K87lObKtWC2xz5qhutHdJf9rr7S8Rq0P7P3PISSgQFyHYl1c8FB2ckAw0j5NX92ZLwpi3Vo/pfSDyPdH2VgrR0LJ6bpnGHJbSIq9Wdy4+ql81t5SCntSYv;
3:xu6oczWWIUB4ZaGMV2AGMx/NgaT9X5jS6rTsSf62O7obrdtDyyDbF6f6nmot8ygtID3kMGGz3xPpy1Slje0msBlD2smUzzZ6AsHraS6Z52Z5si7Q5qXN83oABbqITq+Il+yRwVPSsPIoG3fU1lExzG8BBRTOaEOhi5N+yGCSB7OPtwYW/slfNfVBYAS54sw6uW9CcpipdkCX7TW7A8u/727Q5FFIcnSFI5AdXvqfpbQ=
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR03MB326;
X-Microsoft-Exchange-Diagnostics: 1; BLUPR03MB326;
25:5+cDIAJQ0EkHDVlzX6y2225OBo+MEucfZ7JQ1irmUhA9oP6WgT4GwmUxTAKn6bqh/5ymLU4BCAH75nCF1wLJJMW54jWwwblOBeg3IvO0DjR5PMRO6+VeaOBgJAfE7pjhwYKhjCBfN0v8TWJVHF/GIoQysoECkLVlXX+PDmpAshvpFSJJTHPYbAEtdxwE5thLET61IpUFGFRiMT9HlMcUUncL2156u37cPqs+VzvTnoeyB6xU3L7AU1t8nUuUEPId/zDvsZ4tl3LfVdHR68wp+WFZfBXiIX2PIMHrKe9AM/UP2ai4XBqc5NK0qZUUKAyiCPeGBJKExwJ5X71i2s8kaSzK88GdmH4cSSAo9LTMOXjW6bIiY+TEZdeRU5PkeXPEjiEXPotPD++l5zcRLxnjWrSwEscEhFP1SvH15P5Y7iu8sXNK57a0Xzfjb49V0IiffikijY376Or7gCtqm03uiZig01e+y0QGA0honr1iYUc2kjuAX7IBV7FDXZl0TO6ty2khLIjbn4h/ViX5bx7Hl/xYOzmYV3Z3SCRpvmS9VlzpBvbKAP97idcgZEneJewQX0U+XqglzmdqJ1qIpQglXe9GvykuSaUVePD19oaaVn0LGcIoD4A/5o7cabSqd9ygmEzLT6BnitfwdzmYhF44rc59f9YUCrf73BK5KMxhpzSIg6Gt5FSt1XfN8lHtA/YBkOXy6+0HxEsKPop5550+F5yiORhzTdXs6VYyUaGeP23gY/SfbKLGG/UGAxIQkSQZ
X-Microsoft-Exchange-Diagnostics: 1; BLUPR03MB326;
31:A2TFIDI5BC12y/MLYwb57oZ71VO4hvclk28IYztzkiXAcOKsRFKvc8/PoYEhtQI9oPCB3UGkKaHbY8NWiudYGxm28BpSgRCsJ0CIPToq1yecav0gWDa+F2a3iEYs6mi+fJONoMihgQ8pFuS++Y2cde+dq+kyvX3RncDOxk4fGKK1YNHRVoS1QQ39ma1zWVp4TspLqfaJkGvjj7f+lgDKz57KcF/9EB+CxENspyhbyCEEBiWe6TiqpfZwkeglo8ngitPapPFhzyJdLRGF+Rf3tHbN1UVpghB8Dua0U7MvBRM=;
4:9yQ5UPuLX70HGqa/TEJQZjstrSSZxaL1UsvgA4/HzpsNADk3EvUs/7IsjPHUfYtARnG3dHche1IQ5gCjTYNsOJuoz0NH3Uqno2/MYCkFWojYPMSWbhMc0W22H+7MgrszX8tz29ojlQg3NC+YhQGxiI6CUyfc4sebIipYUdfp9sskl9qQ99erJ4xb/ZlrED56m7ajTdhcxPC3KQbV4LroIeX440vG84GIHNCMZDwXU31SKd3Tni8/qfWo0KuCZa20JPNykjYusKntp+Ovk6FzkEthFo1z+83AEv1aNGv7bAg3NJrkBWpHtyIZnhjdx/ibHPomSxpnLfGPtil11065NkQdGkijTaAVg8Uq7lIs12jNUdazMNoJZFJC5YfEnL6iqcEFoNsDZhWxPb097cXhaFy5UzYSwsojxsTHnUqROAhA8d4B0ppoRhphC+Ou5kfEnw6XMvEBugEkxwKSJqLQk6C8mTPLUZm5WGpWYeK0iUfuyQVPiQ/CTejHkZDCuXdk4G9aBUIhq0gLkl34sTJQvR5Yc6OeC5v1r4ZKwfWL3NU=
X-Microsoft-Antispam-PRVS: <BLUPR03MB3266B033E601F1A5448EE65E6DD0@BLUPR03MB326.namprd03.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(185117386973197);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0;
RULEID:(6040176)(601004)(2401047)(13023025)(13024025)(13017025)(13015025)(13018025)(8121501046)(5005006)(3002001)(10201501046)(6055026);
SRVR:BLUPR03MB326; BCL:0; PCL:0; RULEID:(400006); SRVR:BLUPR03MB326;
X-Forefront-PRVS: 0093C80C01
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BLUPR03MB326;
23:J9gaYfQhQrgQVq132R77uUELsS5Zfc9BagJ6FcJ271?=
=?us-ascii?Q?xwPAZC328ZYnWi+/cGJTtqNyl3xFZqI+csKUI+XfdRF4bll7tMajlnKZbhrD?=
=?us-ascii?Q?MM2VDxcC2GecmY11ytt7CT4ioTSFhLrHG+anYopxD4sdNnh9jq8EUTEbi1KW?=
=?us-ascii?Q?LcxOeB/OMJTqyeK85kmdcByPfmU9qNy8ycxSfp0Rfj3RZouW+dHYMw8X08me?=
=?us-ascii?Q?GbRzGO5Q312RXWfvPy/hCywqIXPsNP9K4kd9GclDi4Uy7IwwFn50FEo640MF?=
=?us-ascii?Q?2Az9jiDYZagC545ZLJgLDTVcZ7+uEkVVWkCKN3DaU74brwM5Fww5yPPwjkvU?=
=?us-ascii?Q?nmJp8IjDT5d0RWyzSsrunG4SHb3v+g5zN4IipIkz3Vu75gnPVnBg2N5aCaRu?=
=?us-ascii?Q?1oJ1SvXn6ZBEQLti7xCTgxQA9gD8xsTEgVHpI9DeLDa2WJFypbd79TDC1u65?=
=?us-ascii?Q?ZvamgvAzRBYKXsFCNN9OZbY6LVT41dSLw3zx7secPJhyH2WnxaNx9LNAV8FX?=
=?us-ascii?Q?jmZxplGwl1sAV2b6Xc4nVGA1LGtE6/xbohPyhCsz5h8wDR2Vtia3pAnDQJ+p?=
=?us-ascii?Q?gfjG5XZf6YIfh5R/85wYr2ip9EBX6fINVR08vjhQkt//qdnwWzHfD4Cxjrji?=
=?us-ascii?Q?EHSAy/tMlPGu4Lw5q6Uh+mbxPjXmeIIn4QFIdVsizfsq2byruKyxIfHO2buc?=
=?us-ascii?Q?n6jNMlrCCf7DLXRnQif7aawvg8P7sQUxj8SLqDcd/lIP+qnwnUcN6eJfI7eQ?=
=?us-ascii?Q?y3romPFTALcTguR6wrPu7kSrNZ3mmnMsG7MQYcd+xZr2lB8MoNHFckXX0OQG?=
=?us-ascii?Q?gULGvAresZbwnrqp8g3xdD/50kE4P/8BRholLZyXx77evY6vbm2yPyeXXEey?=
=?us-ascii?Q?28OXR9GOpIUS7xXqkoSpPx0n4fMHuxOYGllIDZhYQjAtcFU3ZccRHSFNSEmT?=
=?us-ascii?Q?PxdzAyrW4PAWveT6fF25ioV0pNMMIRySDS/ggjzQ+GN6sJixb1hWLa0oXEa+?=
=?us-ascii?Q?PIPx+PPxWFCHsuCTQloMIL9ER08U/ObJSKFbmh6twPkoQyKyexMuyOkZKQph?=
=?us-ascii?Q?YAO83MeBj1cGh+Mxk/za2QvpLAQr4Q/XJL3FuhV7XqIcuIwsKK4P/vNYqvek?=
=?us-ascii?Q?W87Xbftk2UeGYPPAYBa6M+biDyZsgO6Sv1xn/0WQocgAxB+oYm14P4R/Heov?=
=?us-ascii?Q?jIl2K1Jk96iRSmu5Ah3A0bMOrPps13CbEE47cFg2UO9WTOeryjLBE4lwyy4R?=
=?us-ascii?Q?G8BP5zTaNNl/ipQkQRIAxu94H5CKv9YlVTCtg/?=
X-Microsoft-Exchange-Diagnostics: 1; BLUPR03MB326;
6:Ebevz0eM+pGFoJ+XTE1XvS9LFhIf0hNsJwg9YHjbhi31HZRQqSHDrLiBF7mCvx72rHYwfq6eCHzpALgWSnlkelzDFA8VNUdTVqPS0O1b3s30YWwcHGPboA2El2lRygsAUpIN00fFD+LpBkIUoqD01GDNvjOwoNVCj8Fa2Ov6/DS56Xb30HSzVJOZRGQSQEYgVpzVOVLl1zOZ6XsLRKBXU1CLxgPxnRKg9Bgu0HQGVmj3njaO1y44uVYgH2sRSRb0Ig94TRElJbDxubEHCsbP/7usFsKV6P3xtgnVRA2hSuk=;
5:2u73DHwP8sMa/pPmKl+qr0iM9cREjuyFJAX26ZGc5QM8SyRoAJl02gmwUOjG6Vk6iBb1TpxPDaD1kD+b/U2keq2102qVmquupTYA2bJDIEJoayNt0M5vsEpDKiPYtvwGGyzNAsdl/FMkIR5FVDvFB0i810QfnIcFDxB8+w0iUPo=;
24:E2zTSRp599Wt2Pz1KD8mGayaKeGuZVShU9HRXXyunygUYEPk6OW8xunLPzCF2pI4Fdfyav7v/e11A/ENe/577Zy1ylmOkzgZpZf/AvuEkIg=;
7:XL7uzx3+nmkazaNA3CBGwPRelrIBO/q5eihv//RflXBNs5SIk7We7pPDSu3BWwzLSgVVfi3l9+RzDi8fY9G45zAQTyWfpzZ1LUsiE1S4SjuDVN5snWIR3LnTiEbyXjPQdUs78B8KrYSMJOzd62mxL4Wj0biyllfFB0jv0nBotIQmbZzNNn+cyMmwjo/vcIBbn/zESN+HYX/M2YucmS4jmYiVGnkylSuljnXRI35BRPMXmMsqBWYPIwVtlLJQpTZgQXI2KKg5JGn5we9jDB5L5T7wtJQ5y9QGeZZBibQxKG+lxwyb7VmMyU2umAAtv2q8n1wCDnM8GOVdJ0hwMj+02g==
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 12 Oct 2016 05:48:47.3343 (UTC)
X-MS-Exchange-CrossTenant-Id: 5afe0b00-7697-4969-b663-5eab37d5f47e
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=5afe0b00-7697-4969-b663-5eab37d5f47e; Ip=[192.88.168.50];
Helo=[tx30smr01.am.freescale.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB326
Subject: [dpdk-dev] [PATCH v3] test_cryptodev_perf: IV and digest should be
stored at a DMAeble address
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: Wed, 12 Oct 2016 05:48:52 -0000
From: Akhil Goyal <akhil.goyal@nxp.com>
For physical crypto devices, IV and digest are processed by the crypto
device which need the contents to be written on some DMA able address.
So in order to do that, IV and digest are accomodated in the packet.
Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com>
v2: patch rebased
v3: fix broken compilation
---
app/test/test_cryptodev_perf.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/app/test/test_cryptodev_perf.c b/app/test/test_cryptodev_perf.c
index 4aee9af..d498195 100644
--- a/app/test/test_cryptodev_perf.c
+++ b/app/test/test_cryptodev_perf.c
@@ -2722,9 +2722,12 @@ test_perf_set_crypto_op_aes(struct rte_crypto_op *op, struct rte_mbuf *m,
op->sym->auth.aad.length = AES_CIPHER_IV_LENGTH;
/* Cipher Parameters */
- op->sym->cipher.iv.data = aes_iv;
+ op->sym->cipher.iv.data = (uint8_t *)m->buf_addr + m->data_off;
+ op->sym->cipher.iv.phys_addr = rte_pktmbuf_mtophys(m);
op->sym->cipher.iv.length = AES_CIPHER_IV_LENGTH;
+ rte_memcpy(op->sym->cipher.iv.data, aes_iv, AES_CIPHER_IV_LENGTH);
+
/* Data lengths/offsets Parameters */
op->sym->auth.data.offset = 0;
op->sym->auth.data.length = data_len;
@@ -2893,7 +2896,9 @@ test_perf_aes_sha(uint8_t dev_id, uint16_t queue_id,
rte_pktmbuf_free(mbufs[k]);
return -1;
}
-
+ /* Make room for Digest and IV in mbuf */
+ rte_pktmbuf_append(mbufs[i], digest_length);
+ rte_pktmbuf_prepend(mbufs[i], AES_CIPHER_IV_LENGTH);
}
--
2.9.3
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-dev] Project Governance and Linux Foundation
2016-10-12 5:44 [dpdk-dev] Project Governance and Linux Foundation qin.chunhua
@ 2016-10-12 7:43 ` Thomas Monjalon
2016-10-13 6:10 ` [dpdk-dev] [dpdk-users] " Muhammad Zain-ul-Abideen
0 siblings, 1 reply; 7+ messages in thread
From: Thomas Monjalon @ 2016-10-12 7:43 UTC (permalink / raw)
To: qin.chunhua; +Cc: dev, users
Hi,
This is a really interesting use case.
Questions below,
2016-10-12 13:44, qin.chunhua@zte.com.cn:
> ZTE is supportive of improving the DPDK project governance including
> moving the project to the Linux Foundation.
> DPDK has been used in lots of ZTE's equipments and solutions such as
> BBU,RNC,EPC,vEPC,vBRAS,vCPE,vRouter,vSwitch,and so on for many years.
> We have also done some optimization in DPDK.
You mean you made some optimizations to DPDK but keep them secret?
> If the DPDK project governance moves to the Linux Foundation,
> we think this will promote ZTE and other companies to contribute in DPDK.
Why it would help you to contribute?
Why not contribute today?
The project is truly open, a lot of major companies are contributing,
why not yours?
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-dev] [dpdk-users] Project Governance and Linux Foundation
2016-10-12 7:43 ` Thomas Monjalon
@ 2016-10-13 6:10 ` Muhammad Zain-ul-Abideen
0 siblings, 0 replies; 7+ messages in thread
From: Muhammad Zain-ul-Abideen @ 2016-10-13 6:10 UTC (permalink / raw)
To: Thomas Monjalon; +Cc: qin.chunhua, dev, users
I agree with Mr. Thomas Monjalon. Any optimization in DPDK structure should
be made open.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-dev] [dpdk-users] Project Governance and Linux Foundation
2016-10-17 14:40 ` O'Driscoll, Tim
@ 2016-10-18 13:22 ` Thomas Monjalon
0 siblings, 0 replies; 7+ messages in thread
From: Thomas Monjalon @ 2016-10-18 13:22 UTC (permalink / raw)
To: O'Driscoll, Tim; +Cc: users, dev
2016-10-17 14:40, O'Driscoll, Tim:
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > 2016-10-17 11:52, O'Driscoll, Tim:
> > > From: Hobywan Kenoby
> > > > The current DPDK version can run on virtually all processors (Intel,
> > > > IBM and ARM) and leverage all NICs: is there **really** anyone
> > > > questionning openness of the community?
> > >
> > > I still hear concerns on this, and based on discussions with others
> > > who put their names to the post below, they do too.
> > > I think it's a perception that we need to address.
> >
> > It is simple to address this perception with fact checking.
> > The next releases will provide even more code for ARM and NPUs.
> > If someone submits some good code and is ignored, it is easy enough
> > to ping the mailing list and make it visible.
> > If someone sees any regression on his architecture, we care.
> > Please let's stop maintaining confusion on this topic.
> >
> > DPDK *is* truly open.
>
> Well, to be a little more specific, the concern I've heard on many occasions is that 6WIND control the infrastructure for the project and so effectively have a veto over what's accepted into DPDK. Your argument is that you've never exercised that veto, which is true, but you still have the ability to do so. That's not a characteristic of a truly open project. As stated in the original post on this:
>
> > - The infrastructure for a project like DPDK should not be owned and controlled by any single company.
Technically yes, we can improve that part, at the cost of more coordination
with more administrators, and without being sure that everybody will trust
this new organization.
I would like to highlight that this supposed veto cannot really be exercised
because feedbacks are open on the mailing list.
I'm worried that we are talking too much about a veto situation which
does not happen, and would mean ignoring some comments, whereas the real
issue is the lack of reviews.
Apart that, I still think such organization can be interesting for other
(legals and budget) reasons.
At this point, I must admit that moving the project infrastructure will have
at least one big benefit: stopping this kind of discussion.
And such discussion will probably never happen again because nobody will
take the risk of annoying the big vendors supporting the new organization.
One can wonder whether it is an improvement.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-dev] [dpdk-users] Project Governance and Linux Foundation
[not found] ` <20161018121629630001294@chinamobile.com>
@ 2016-10-18 12:51 ` Thomas Monjalon
0 siblings, 0 replies; 7+ messages in thread
From: Thomas Monjalon @ 2016-10-18 12:51 UTC (permalink / raw)
To: Liu Yuan
Cc: users, O'Driscoll, Tim, dev, 'Yan, Feng A', denglingli
2016-10-18 12:16, Liu Yuan:
> China Mobile would like to support moving the DPDK project to the Linux Foundation.
OK, there can be some advantages to join the Linux Foundation.
> DPDK is a key technology / element in the NFV. As an end user, we can foresee the importance of DPDK in the future. If the DPDK project could be governed by Linux Foundation, it will promote more companies to join in and contribute to DPDK project.
Same question as for ZTE,
Why joining the Linux Foundation would help you to contribute?
Is there an issue related to your patents?
How to help you, specifically?
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-dev] [dpdk-users] Project Governance and Linux Foundation
2016-10-17 12:40 ` [dpdk-dev] [dpdk-users] " Thomas Monjalon
@ 2016-10-17 14:40 ` O'Driscoll, Tim
2016-10-18 13:22 ` Thomas Monjalon
0 siblings, 1 reply; 7+ messages in thread
From: O'Driscoll, Tim @ 2016-10-17 14:40 UTC (permalink / raw)
To: Thomas Monjalon, users, dev; +Cc: Hobywan Kenoby
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Monday, October 17, 2016 1:41 PM
> To: users@dpdk.org; dev@dpdk.org
> Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>; Hobywan Kenoby
> <hobywank@hotmail.com>
> Subject: Re: [dpdk-users] Project Governance and Linux Foundation
>
> 2016-10-17 11:52, O'Driscoll, Tim:
> > From: Hobywan Kenoby
> > > The current DPDK version can run on virtually all processors (Intel,
> IBM
> > > and ARM) and leverage all NICs: is there **really** anyone
> questionning
> > > openness of the community?
> >
> > I still hear concerns on this, and based on discussions with others
> who
> > put their names to the post below, they do too.
> > I think it's a perception that we need to address.
>
> It is simple to address this perception with fact checking.
> The next releases will provide even more code for ARM and NPUs.
> If someone submits some good code and is ignored, it is easy enough
> to ping the mailing list and make it visible.
> If someone sees any regression on his architecture, we care.
> Please let's stop maintaining confusion on this topic.
>
> DPDK *is* truly open.
Well, to be a little more specific, the concern I've heard on many occasions is that 6WIND control the infrastructure for the project and so effectively have a veto over what's accepted into DPDK. Your argument is that you've never exercised that veto, which is true, but you still have the ability to do so. That's not a characteristic of a truly open project. As stated in the original post on this:
> - The infrastructure for a project like DPDK should not be owned and controlled by any single company.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-dev] [dpdk-users] Project Governance and Linux Foundation
2016-10-17 11:52 ` O'Driscoll, Tim
@ 2016-10-17 12:40 ` Thomas Monjalon
2016-10-17 14:40 ` O'Driscoll, Tim
0 siblings, 1 reply; 7+ messages in thread
From: Thomas Monjalon @ 2016-10-17 12:40 UTC (permalink / raw)
To: users, dev; +Cc: O'Driscoll, Tim, Hobywan Kenoby
2016-10-17 11:52, O'Driscoll, Tim:
> From: Hobywan Kenoby
> > The current DPDK version can run on virtually all processors (Intel, IBM
> > and ARM) and leverage all NICs: is there **really** anyone questionning
> > openness of the community?
>
> I still hear concerns on this, and based on discussions with others who
> put their names to the post below, they do too.
> I think it's a perception that we need to address.
It is simple to address this perception with fact checking.
The next releases will provide even more code for ARM and NPUs.
If someone submits some good code and is ignored, it is easy enough
to ping the mailing list and make it visible.
If someone sees any regression on his architecture, we care.
Please let's stop maintaining confusion on this topic.
DPDK *is* truly open.
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2016-10-18 13:22 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-10-12 5:44 [dpdk-dev] Project Governance and Linux Foundation qin.chunhua
2016-10-12 7:43 ` Thomas Monjalon
2016-10-13 6:10 ` [dpdk-dev] [dpdk-users] " Muhammad Zain-ul-Abideen
-- strict thread matches above, loose matches on Subject: below --
2016-10-10 8:33 [dpdk-dev] " O'Driscoll, Tim
2016-10-17 10:23 ` Hobywan Kenoby
2016-10-17 11:52 ` O'Driscoll, Tim
2016-10-17 12:40 ` [dpdk-dev] [dpdk-users] " Thomas Monjalon
2016-10-17 14:40 ` O'Driscoll, Tim
2016-10-18 13:22 ` Thomas Monjalon
[not found] ` <20161018121629630001294@chinamobile.com>
2016-10-18 12:51 ` Thomas Monjalon
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).