From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id ECD5A1B4CD for ; Fri, 15 Feb 2019 22:05:36 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 8D86C21F60; Fri, 15 Feb 2019 16:05:36 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 15 Feb 2019 16:05:36 -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=quP4AIYL7Mk6KYgIk4BCM66fvTo8iLUp7zdq4JceUS0=; b=p2F+o7lOpW0G B6Y9NfwjfMAhYSoxMhVMS5CXNX+buSdnTDLN2ZHHmnHom9N5fd8Lq4gmGUmMfW7o RlWLfPuPQNPAvGfXL1lQx60mh0FdPW5I3x4oakf+a4Z4UWppSN6dmjdyIozPIO+o G7LIbvdLYdHvO7HF3CW3B3DC4/Gp3Io= 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=quP4AIYL7Mk6KYgIk4BCM66fvTo8iLUp7zdq4JceU S0=; b=VIFqgH1gx7iuk+28oC7sSDVFeReG/cCfR2JYHCDSC2Oua7AepwBtphelM r0bg5oV3YNRffgbWNUEmgZaZNJOTu07edjWj42z9HeHtQLh50rXqFHkTT5CGnnVp PM9a697KQIapnXCTnsUM6W8iUMzvSYvRAlTgyJjY/n+T6+wMKm9UtfS4tzz1wUAy UMv7Ts/lFmGqKTcS2PSEJa/lHwiD0jdGEtcrLn9EieDRJrW29H/9RO3K59MnXa4D IGyQUskcV95G8UQBOKLdOmZzQYgHVWzkHgLDBXPtuI60ke+CCTvZUX4MKkCIFBMx h+7rcLGZrUf7nuj/luc4dNIeoxQVA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledruddtjedgudegiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecu fedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvufffkf gjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhn uceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuffhomhgrihhnpeguphgukh drohhrghenucfkphepjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhl fhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuih iivgeptd 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 74BC1E4680; Fri, 15 Feb 2019 16:05:35 -0500 (EST) From: Thomas Monjalon To: Marko Kovacevic Cc: web@dpdk.org, john.mcnamara@intel.com, tim.odriscoll@intel.com Date: Fri, 15 Feb 2019 22:05:34 +0100 Message-ID: <2073329.GrbqgB35EI@xps> In-Reply-To: <20190215164337.38535-1-marko.kovacevic@intel.com> References: <20190215164337.38535-1-marko.kovacevic@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-web] [PATCH] update Intel roadmap for 19.05 X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK website maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Feb 2019 21:05:37 -0000 15/02/2019 17:43, Marko Kovacevic: > Intel roadmap is announced in the dpdk-dev mailing list: > http://mails.dpdk.org/archives/dev/2019-February/124766.html > > Signed-off-by: Marko Kovacevic > --- > +- QAT asymmetric crypto with support for modexp and modinv > +- QAT compression PMD support for large scatter-gather lists > +- add a DPDK PMD to support AF_XDP > +- support for additional crypto/auth algorithms in the ipsec library > +- initial support for DPDK on Windows > +- add new baseband device turbo PMD I changed the order to sort it like in the release notes, and did few small rewords, hence Signed-off-by: Thomas Monjalon and applied: http://core.dpdk.org/roadmap/ I'm surprised you did not mention virtio optimisations and non-blocking stack mempool handler. Is there any specific reason?