From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 31C8BDDF23 for ; Sat, 20 Oct 2007 01:47:42 +1000 (EST) In-Reply-To: <200710191937.23638.yur@emcraft.com> References: <200710181108.19413.yur@emcraft.com> <18199.60025.563689.10810@cargo.ozlabs.ibm.com> <200710191937.23638.yur@emcraft.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: From: Kumar Gala Subject: Re: [PATCH] ppc44x: support for 256K PAGE_SIZE Date: Fri, 19 Oct 2007 10:48:01 -0500 To: Yuri Tikhonov Cc: linuxppc-dev@ozlabs.org, Paul Mackerras List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Oct 19, 2007, at 10:37 AM, Yuri Tikhonov wrote: > On Friday 19 October 2007 03:21, Paul Mackerras wrote: >> Have you measured the performance using a 64kB page size? If so, how >> does it compare with the 256kB page size? > > I measured the performance of the sequential full-stripe write > operations to > a RAID-5 array (P values below are in MB per second) using the h/w > accelerated > RAID-5 driver. > > Here are the comparative results for the different PAGE_SIZE values: > > PAGE_SIZE = 4K: > P = 66 MBps; > > PAGE_SIZE = 16K: > P = 145 MBps; > > PAGE_SIZE = 64K: > P = 196 MBps; > > PAGE_SIZE = 256K: > P = 217 MBps. Is this all in kernel space? or is there a user space aspect to the benchmark? >> The 64kB page size has the attraction that no binutils changes are >> required. > > That's true, but the additional performance is an attractive thing > too. - k