From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f169.google.com (mail-pf0-f169.google.com [209.85.192.169]) by dpdk.org (Postfix) with ESMTP id 96172475E for ; Tue, 6 Dec 2016 22:29:51 +0100 (CET) Received: by mail-pf0-f169.google.com with SMTP id i88so72112348pfk.2 for ; Tue, 06 Dec 2016 13:29:51 -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=VFi8Sldv6Qy9rfzq5lOlW5sLjSg1RaC6fODWsDXg89I=; b=vxyEjhUVLDey5V/i6ObMlPjKLUysljDxKuquk7niM3yw8zpKgRk6EssiIsPH9snIDC LsYYEQ3UslZfgJ4WMMhL9l8TdcAiIZhqaeqfqRGqVnj++koWQOG6r7gkAOLG+xf/MPOE JyTz/m/JXnk6Qp1SNqVKC+UEgDHLdTqZVxHNHI+cCPfsrmFpDgLT+22H/YSAKYkLHBS7 Iw9D0/CA0f+/RrnoZuWrdTNCnr6Bnk1LAfs3Fa/PXLsZ7xkP5ZXOq0RK8qk9WBOwTLwU TtDBiuI2EMxsF2YerljSd2OOzYqtGFoEkGVQVXnjNzw/1T8Iyv6Iv3RPoc2mN9VDQKI1 WZFQ== 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=VFi8Sldv6Qy9rfzq5lOlW5sLjSg1RaC6fODWsDXg89I=; b=YVe2iivvUEhELX4Bt1TbT2oLStNFUvlQCL/MtU/QMArJzmN4DLYMFgYaecU+TseCf9 t3jjauCb9Hp46W5Ej6BrEixhTRk91L7bvXPwhuZl95OkXosXAK2HrE64CZKzrX/cEHVw NT4HvBOKjz78AxOwGHb5jjK2Jv1LAi+1JzRDRWFAJUPIDiUdLONjmcEvnGgqvKc/S859 wqmInhlgNCRsK5uj99vrGVP3QHU/75LPM6YWSAz4s03H2vR33Rzeqz+xtEuUBBXK4kIU jiz8rZi1JLLwvjKFL9OP0dRGOWLxwH1dv2NZGrsSD6Q9hPiVRer/MHurI/GJpgJ6TCsd OfTA== X-Gm-Message-State: AKaTC00KYahw4GhgFTXFp+NSvGOKxEL9wxEIljV393+lZbocHLWJ4QuN9m6XkFIDfSbIcQ== X-Received: by 10.98.71.218 with SMTP id p87mr65281782pfi.125.1481059790813; Tue, 06 Dec 2016 13:29:50 -0800 (PST) Received: from xeon-e3 (204-195-18-65.wavecable.com. [204.195.18.65]) by smtp.gmail.com with ESMTPSA id 2sm37133464pgy.27.2016.12.06.13.29.50 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 06 Dec 2016 13:29:50 -0800 (PST) Date: Tue, 6 Dec 2016 13:29:43 -0800 From: Stephen Hemminger To: Thomas Monjalon Cc: Varun , dev@dpdk.org Message-ID: <20161206132943.5ff2d74f@xeon-e3> In-Reply-To: <1929209.d2FdTvr7Hj@xps13> References: <2702523.1trrNuZT35@xps13> <20161206122531.4d147748@xeon-e3> <1929209.d2FdTvr7Hj@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 21:29:52 -0000 On Tue, 06 Dec 2016 22:25:29 +0100 Thomas Monjalon wrote: > 2016-12-06 12:25, Stephen Hemminger: > > 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. > > I don't understand what you mean. The code from Brocade was on older release, and depended on a slightly different model for UIO interaction. Resolving this has taken longer than expected. Also the changes from The changes to PCI for v16.11 overlapped vmbus related changes.