From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753236AbbCEAsG (ORCPT ); Wed, 4 Mar 2015 19:48:06 -0500 Received: from aserp1040.oracle.com ([141.146.126.69]:30161 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751171AbbCEAsE (ORCPT ); Wed, 4 Mar 2015 19:48:04 -0500 Message-ID: <54F7A796.7080003@oracle.com> Date: Thu, 05 Mar 2015 08:47:18 +0800 From: Bob Liu User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4 MIME-Version: 1.0 To: Konrad Rzeszutek Wilk CC: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= , Felipe Franciosi , David Vrabel , "xen-devel@lists.xen.org" , "linux-kernel@vger.kernel.org" , "axboe@fb.com" , "hch@infradead.org" , "avanzini.arianna@gmail.com" , chegger@amazon.de Subject: Re: [PATCH 04/10] xen/blkfront: separate ring information to an new struct References: <54E4CBD1.1000802@citrix.com> <20150218173746.GF8152@l.oracle.com> <9F2C4E7DFB7839489C89757A66C5AD629EB997@AMSPEX01CL03.citrite.net> <54E544CC.4080007@oracle.com> <54E5C444.4050100@citrix.com> <54E5C59F.2060300@citrix.com> <9F2C4E7DFB7839489C89757A66C5AD629EDBBA@AMSPEX01CL03.citrite.net> <54E5E13E.9040502@citrix.com> <20150220185937.GC1749@l.oracle.com> <54F068A8.4010606@oracle.com> <20150304212140.GA18253@l.oracle.com> In-Reply-To: <20150304212140.GA18253@l.oracle.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Source-IP: ucsinet22.oracle.com [156.151.31.94] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/05/2015 05:21 AM, Konrad Rzeszutek Wilk wrote: >>> David assertion that better performance and scalbility can be gained >>> with grant table locking and TLB flush avoidance is interesting - as >>> 1). The grant locking is going in Xen 4.6 but not earlier - so when running >>> on older hypervisors this gives an performance benefit. >>> >>> 2). I have not seen any prototype TLB flush avoidance code so not know >>> when that would be available. >>> >>> Perhaps a better choice is to do the removal of the persistence support >>> when the changes in Xen hypervisor are known? >>> >> >> With patch: [PATCH v5 0/2] gnttab: Improve scaleability, I can get >> nearly the same performance as without persistence support. >> >> But I'm not sure about the benchmark described here: >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/xen-blkfront.c?id=0a8704a51f386cab7394e38ff1d66eef924d8ab8 > > Meaning you weren't able to do the same test? > I can if there are more details about how to set up this 5 and 10 guests environment and test pattern have been used. Just think it might be save time if somebody still have the similar environment by hand. Roger and Felipe, if you still have the environment could you please have a quick compare about feature-persistent performance with patch [PATCH v5 0/2] gnttab: Improve scaleability? Thanks, -Bob