Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754074AbZAKT17 (ORCPT ); Sun, 11 Jan 2009 14:27:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751734AbZAKT1r (ORCPT ); Sun, 11 Jan 2009 14:27:47 -0500 Received: from wf-out-1314.google.com ([209.85.200.175]:44339 "EHLO wf-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752043AbZAKT1q (ORCPT ); Sun, 11 Jan 2009 14:27:46 -0500 Date: Sun, 11 Jan 2009 11:27:42 -0800 From: Nifty Fedora Mitch To: Justin Piszcz Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org, linux-ide-arrays@lists.math.uh.edu Subject: Re: [Benchmarks] How do I set the memory invalidate bit for a 3ware 9550SXU-12 controller? Message-ID: <20090111192742.GA3784@compegg.wr.niftyegg.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1428 Lines: 27 On Thu, Jan 08, 2009 at 09:20:30AM -0500, Justin Piszcz wrote: > Subject: [Benchmarks] How do I set the memory invalidate bit for a 3ware 9550SXU-12 controller? > > System = RHEL5 x86_64 > Kernel = 2.6.18-53.1.13.el5 > > Per: http://makarevitch.org/rant/raid/ > It states: "A potential culprit, at least for slow write operations, lies in Q12546. I played with setpci in order to enable this ''Memory Write and Invalidate' (lspci now shows that the 3Ware controller 9550 is in 'MemWINV+' instead of 'MemWINV-' mode), maybe enhancing write throughput. The 9650 is in 'MemWINV-' mode. This seems somewhat frequent with SuperMicro mainboards, check this with your system integrator or SuperMicro support service. This may be somewhat tied to the "interleaved memory". With the 9650 my PCI parameters are as follows:" > > Links to: http://www.3ware.com/KB/article.aspx?id=12546 > > How do I change MemWINV+ to MemWINV- using setpci? Since this is a SuperMicro motherboard double check the BIOS settings involved with MTRR registers. Since Windows uses PAT its drivers will often ignore BIOS settings that Linux will not. -- T o m M i t c h e l l Found me a new hat, now what? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/