From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 9330E1B2AB for ; Sun, 2 Dec 2018 01:17:12 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 2EADA21687; Sat, 1 Dec 2018 19:17:12 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sat, 01 Dec 2018 19:17:12 -0500 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=BEWaFuSMZm9USghoyMVhEdQd8oNld8qn7XOqgtxL/ew=; b=PfhLYL1B3vRL HRgAidgilVPQQfbvyBs0DvS9sUmu7sxnuNk0dOCa+2o0VDReNHMKyaV3gBw1Mf6c 0S6gYOaydrlVeaL0h6zxvoX6mDqZHqZgSZokO6+/yuv8iFDDB00UaRdGXy7o/qeY p1q1napbX8lVga9eCaj5zHk91Fsp8/s= 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=fm1; bh=BEWaFuSMZm9USghoyMVhEdQd8oNld8qn7XOqgtxL/ ew=; b=KdYE6sylIXR3O+7l/CtfBXuQN+oXJK7bKoRVrclTuO+Zke2oGD5Q0dSAG jdBIK0q9aDLZrSka/+MSnAk2F5otALnp9lkLDmBw/ps5kpFS+ILGX7l4K2qfLumt DB/3Iea+TUIQ/D7vbDqt1gh2a2XyA3FVxIhrbPCQOr2kf9pEiKpo+7uji4Um7EC8 qcBnpFcirRzqcStxueo0LeNLxbmiz1D9hBfVR8eMYnyOh3ivfDBbPtZx76UKMVYB K/ERl0tc77jwkFEJg3ApZyUDzDFvqd6EPnZqPI8M+0oLNcVItYMpCJJMxS5wmUKD YoK0KF6r3zZhpV142JTvLuVi2INEw== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (c-73-70-89-93.hsd1.ca.comcast.net [73.70.89.93]) by mail.messagingengine.com (Postfix) with ESMTPA id 144E3102E8; Sat, 1 Dec 2018 19:17:10 -0500 (EST) From: Thomas Monjalon To: "O'Driscoll, Tim" Cc: dev@dpdk.org Date: Sun, 02 Dec 2018 01:17:09 +0100 Message-ID: <2348857.k0IvZTluD0@xps> In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BAB77C1B20@IRSMSX108.ger.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BAB77C1B20@IRSMSX108.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] 19.02 Intel Roadmap 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: Sun, 02 Dec 2018 00:17:12 -0000 Hi, 23/11/2018 12:11, O'Driscoll, Tim: > As discussed at yesterday's Release Status Meeting, we need to update our Roadmap page (http://core.dpdk.org/roadmap/) for 19.02. The features that we plan to contribute are described below. We'll submit a patch to update the roadmap page with this info. > > > vDPA Live Migration Software Fallback: The current vDPA library provides the vDPA driver an interface to implement hardware-based dirty page logging. A software fallback option will be added to handle situations where the hardware does not log dirty pages. > > IPsec Library: An initial version of a DPDK IPsec library will be provided. This will define data structures and APIs to prepare IPsec data for crypto processing, APIs to handle ESP header encap/decap for tunnel and transport modes, and capabilities such as initialising Security Associations. The existing IPsec Security Gateway sample application (ipsec-secgw) will be updated to use the new library. > > Compression Performance Test Tool: A performance test application will be created which will allow performance testing of compression PMDs. > > I40E Queue Request: A new operation (VIRTCHNL_OP_REQUEST_QUEUES) will be implemented to allow an I40E VF to request a specific number of queues from the PF. What about the new PMD ice for Intel E810? https://patches.dpdk.org/cover/48285/ It is not planned to be part of DPDK 19.02?