From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 1E1E46880 for ; Sat, 22 Nov 2014 00:41:15 +0100 (CET) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga102.fm.intel.com with ESMTP; 21 Nov 2014 15:51:51 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.97,862,1389772800"; d="scan'208";a="420042603" Received: from kmsmsx152.gar.corp.intel.com ([172.21.73.87]) by FMSMGA003.fm.intel.com with ESMTP; 21 Nov 2014 15:42:18 -0800 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by KMSMSX152.gar.corp.intel.com (172.21.73.87) with Microsoft SMTP Server (TLS) id 14.3.195.1; Sat, 22 Nov 2014 07:51:49 +0800 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.182]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.86]) with mapi id 14.03.0195.001; Sat, 22 Nov 2014 07:51:47 +0800 From: "Zhu, Heqing" To: "O'driscoll, Tim" , "Carew, Alan" , Thomas Monjalon Thread-Topic: [dpdk-dev] [PATCH v4 00/10] VM Power Management Thread-Index: AQHP5lPn0Uf2LDzt6UWhp/KXyjo0rZwt9SWAgAEPbICAACi/gIADKZ6AgBLb3wCAFAWBAIAAk50AgBG7/YA= Date: Fri, 21 Nov 2014 23:51:47 +0000 Message-ID: References: <1412003903-9061-1-git-send-email-alan.carew@intel.com> <3349663.LNtcecTXb3@xps13> <0E29434AEE0C3A4180987AB476A6F6306D2811AD@IRSMSX109.ger.corp.intel.com> <1804867.TWdiCQc2JQ@xps13> <0E29434AEE0C3A4180987AB476A6F6306D28E7DF@IRSMSX109.ger.corp.intel.com> <26FA93C7ED1EAA44AB77D62FBE1D27BA54C4BD63@IRSMSX102.ger.corp.intel.com> In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C4BD63@IRSMSX102.ger.corp.intel.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH v4 00/10] VM Power Management X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Nov 2014 23:41:16 -0000 Pablo just sent a new patch set. This is a significant effort and it addres= sed a valid technical problem statement.=20 I express my support to this feature into the DPDK mainline.=20 IMHO, the previous *rejection* reason are not solid. It is important to enc= ourage the real contribution like this.=20 -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of O'driscoll, Tim Sent: Monday, November 10, 2014 10:54 AM To: Carew, Alan; Thomas Monjalon Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH v4 00/10] VM Power Management > From: Carew, Alan >=20 > > Did you make any progress in Qemu/KVM community? > > We need to be sync'ed up with them to be sure we share the same goal. > > I want also to avoid using a solution which doesn't fit with their plan= . > > Remember that we already had this problem with ivshmem which was=20 > > planned to be dropped. > > . . . >=20 > Unfortunately, I have not yet received any feedback: > http://lists.nongnu.org/archive/html/qemu-devel/2014-11/msg01103.html Just to add to what Alan said above, this capability does not exist in qemu= at the moment, and based on there having been no feedback on the qemu mail= ing list so far, I think it's reasonable to assume that it will not be impl= emented in the immediate future. The VM Power Management feature has also b= een designed to allow easy migration to a qemu-based solution when this is = supported in future. Therefore, I'd be in favour of accepting this feature = into DPDK now. It's true that the implementation is a work-around, but there have been sim= ilar cases in DPDK in the past. One recent example that comes to mind is us= erspace vhost. The original implementation could also be considered a work-= around, but it met the needs of many in the community. Now, with support fo= r vhost-user in qemu 2.1, that implementation is being improved. I'd see VM= Power Management following a similar path when this capability is supporte= d in qemu. Tim