linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: [Benchmarks] How do I set the memory invalidate bit for a 3ware 9550SXU-12 controller?
Date: Thu, 08 Jan 2009 23:52:21 +0000	[thread overview]
Message-ID: <496691B5.2020607@anonymous.org.uk> (raw)
In-Reply-To: <alpine.DEB.1.10.0901080846430.29454@p34.internal.lan>

On 08/01/2009 14:20, Justin Piszcz wrote:
> System = RHEL5 x86_64
> Kernel = 2.6.18-53.1.13.el5

Not on the topic of your query, but why are you running a year-old 
kernel? There have been about 10 updates since then.

[...]
> Also tried:
> # setpci -d *:* e6.b=2e

Eeek, don't do that, that's asking for trouble, throwing settings at 
every PCI device in your system. Really, you should look up the PCI spec 
and see.

If you're sure you're not going to hose your system and lose data, or 
you don't care for the sake of experiment, you might try:

# setpci -s 03:01.0 COMMAND=0:0010

that's -s 03:01.0 to select your card by its bus and slot, COMMAND to 
play with the command register, 0 to set to zero, 0010 as a mask to 
affect only bit 4. But I may have got it wrong - as I said you should 
look up the PCI spec for yourself, as well as the setpci man page - and 
in any case I take no responsibility if it goes wrong.

Cheers,

John.

  parent reply	other threads:[~2009-01-08 23:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 14:20 [Benchmarks] How do I set the memory invalidate bit for a 3ware 9550SXU-12 controller? Justin Piszcz
2009-01-08 15:04 ` David Lethe
2009-01-08 22:52 ` adam radford
2009-01-08 23:52 ` John Robinson [this message]
2009-01-11 19:27 ` Nifty Fedora Mitch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=496691B5.2020607@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).