From: Philipp Rumpf <prumpf@parcelfarce.linux.theplanet.co.uk>
To: Drew Hess <dhess@CS.Stanford.EDU>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i850 support
Date: Sun, 17 Dec 2000 09:07:09 +0000 [thread overview]
Message-ID: <20001217090709.D21944@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <Pine.GSO.4.21.0012170028520.6727-100000@Xenon.Stanford.EDU>
In-Reply-To: <Pine.GSO.4.21.0012170028520.6727-100000@Xenon.Stanford.EDU>; from dhess@CS.Stanford.EDU on Sun, Dec 17, 2000 at 12:52:59AM -0800
On Sun, Dec 17, 2000 at 12:52:59AM -0800, Drew Hess wrote:
> It also contains an experimental patch to drivers/pci/quirks.c that forces
> standby mode for pool C RDRAM devices. I've seen some benchmarks
> comparing the Intel D850GB motherboard to the ASUS P4T and attributing the
> better performance of the P4T to the fact that Intel's BIOS puts pool C
> RDRAM in nap mode and has no option to change it, whereas the P4T does.
> On my D850GB, the patch doesn't seem to change the performance of STREAM
> one way or the other; but when I change the value written into the RDST
> register to set nap mode and shrink the A and B pools to 1 device each, I
> see about a 20-30MB/s drop-off on STREAM, so I'm pretty sure the code does
> what it's supposed to.
>
> This code isn't strictly a 'quirk' in the sense that some of the bug
> workarounds in drivers/pci/quirks.c are, but I didn't see a more
> appropriate place to put it. Suggestions are welcome.
sounds like powertweak is what you want.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-17 9:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-17 8:52 Drew Hess
2000-12-17 9:07 ` Philipp Rumpf [this message]
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=20001217090709.D21944@parcelfarce.linux.theplanet.co.uk \
--to=prumpf@parcelfarce.linux.theplanet.co.uk \
--cc=dhess@CS.Stanford.EDU \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®