From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f51.google.com (mail-pg0-f51.google.com [74.125.83.51]) by dpdk.org (Postfix) with ESMTP id 3E1BA2BCD for ; Tue, 6 Dec 2016 21:25:41 +0100 (CET) Received: by mail-pg0-f51.google.com with SMTP id 3so152904802pgd.0 for ; Tue, 06 Dec 2016 12:25:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=bSCUD7Dc0GLEDhKu73oDBS/zuZYjeONL9eZyg2Hs7Hs=; b=UOmxQADpufNqufYc8+Kse1DmZA4YyNwQ3qP5ChmzrMqla9+4P/99ZlMCsWXHyrinTK FdemndEwBSlumqA/o8CK5cWeunVK0+ci0MLwHOtnog0A9aPr9nJb2IPcUIkLM1J9rFTk CxRjsw3PXt7qZkK95mpgSGQDznvvHiwHdg03KFtL3qDrzvZIG6JdjnWwSD3XEABCS+7x bb0nQ6EjbpeCXKcp/svSHdyehcPDa3BKbWcMI0L2J2IQXEB1SJYOhvCtbhMCzPk+0YqQ lFpn1Mil7cphiPFCQHvf8yYJGeCMZBi4a62OTb2AXildeLJPpSbScz4Ix3HrDQXCpBzb P4yA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=bSCUD7Dc0GLEDhKu73oDBS/zuZYjeONL9eZyg2Hs7Hs=; b=hNzYYx0gEYq+GeQ8yjWrdIp4USgADtYQaF9V0XubZ/38I8BmcmHuFEzgQ9YoghBDfq pVblxHHO/dAyUg0uqqHoPBbjekP0kLFxCl8vTYoY6XlLa5HTu+ScyxW6Q7EtOxuZoxBs giYuiEJRGN5KWhiEj5gGK7FpJMMeoXildlt34Znm5A4kMjRdv45mWTnHJFDtPNaWJick XZP6NxlIYph1RzQD6gHAKdEdiNiEO2nqyEptusgaliTU0hygC7G8kcMk3wPVOXHtr9Ql 97+sm9ictVILfsz7YqA8zLh95Bx5i7ox0Jzzp1T4HX1wtdHNrRB+RgnJeXQEiXv56BnH BNww== X-Gm-Message-State: AKaTC01Yc9SCWWqfPBLXDD9t903jneF0hTbm9vo+3qI0JIZIJ2/zWAu5KZKFMq4k1vWiPg== X-Received: by 10.99.37.195 with SMTP id l186mr113993307pgl.91.1481055940542; Tue, 06 Dec 2016 12:25:40 -0800 (PST) Received: from xeon-e3 (204-195-18-65.wavecable.com. [204.195.18.65]) by smtp.gmail.com with ESMTPSA id 65sm36880106pfl.21.2016.12.06.12.25.40 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 06 Dec 2016 12:25:40 -0800 (PST) Date: Tue, 6 Dec 2016 12:25:31 -0800 From: Stephen Hemminger To: Thomas Monjalon Cc: Varun , dev@dpdk.org Message-ID: <20161206122531.4d147748@xeon-e3> In-Reply-To: <2702523.1trrNuZT35@xps13> References: <2343421.PKDcrM7tSE@xps13> <2702523.1trrNuZT35@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] Hyper-v support 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, 06 Dec 2016 20:25:41 -0000 On Thu, 01 Dec 2016 12:25:10 +0100 Thomas Monjalon wrote: > (fixed the email, sorry) > > 2016-12-01 12:21, Thomas Monjalon: > > 2016-11-30 14:34, Varun: > > > Hi, > > > > > > I would like to know if the latest DPDK (16.11) supports hyper-v? > > > > > > I couldn't find any conclusive evidence online or in dpdk roadmap. Is it > > > likely that we see it in 17.05? > > > > Stephen did a presentation at the last DPDK userspace summit: > > https://dpdksummit.com/Archive/pdf/2016Userspace/Day01-Session03-StephenHemminger-Userspace2016.pdf > > > > Stephen, please, could you confirm the expected release for Hyper-V support? > > A patch for the roadmap page would be great: > > http://dpdk.org/dev/roadmap > > Yes, the plan is the same. Since DPDK is moving target, getting merges done has been a real pain. The Hyper-V UIO generic driver has just gone into upstream next tree. Therefore the driver will depend on 4.10 kernel initially.