From: mbs <mbs@mc.com>
To: Chris Friesen <cfriesen@nortelnetworks.com>, Brien <admin@brien.com>
Cc: John Bradford <john@grabjohn.com>, linux-kernel@vger.kernel.org
Subject: Re: my dual channel DDR 400 RAM won't work on any linux distro
Date: Thu, 17 Apr 2003 07:46:37 -0500 [thread overview]
Message-ID: <200304171241.IAA08069@mc.com> (raw)
In-Reply-To: <3E9D8062.1060202@nortelnetworks.com>
On Wednesday 16 April 2003 12:10, Chris Friesen wrote:
>
> Linux often shows up memory problems when M$ doesn't since it is a) more
> aggressive in its use of memory, and b) capable of driving cpu and chipset
> closer to their theoretical limits.
>
<not flamebait, honest question>
you hear this all the time, but do we really have any empirical evidence
proving this, or is it just what we say to make ourselves feel good when
Linux won't run on hardware that works fine under other os's?
</not flamebait, honest question>
next prev parent reply other threads:[~2003-04-17 12:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200304161511.h3GFBoe7000614@81-2-122-30.bradfords.org.uk>
2003-04-16 15:41 ` my dual channel DDR 400 RAM won't work on any linux distro Brien
2003-04-16 15:47 ` Mr. James W. Laferriere
2003-04-16 15:58 ` Charles Cazabon
2003-04-16 16:10 ` Chris Friesen
2003-04-17 12:46 ` mbs [this message]
2003-04-17 12:45 ` Alan Cox
[not found] ` <1050506129.28586.121.camel@dhcp22.swansea.linux.org.uk>
2003-04-16 16:38 ` Brien
2003-04-16 17:01 ` John Bradford
2003-04-16 18:15 ` Brien
2003-04-16 19:28 ` John Bradford
2003-04-16 20:51 ` Brien
2003-04-17 8:12 ` John Bradford
2003-04-20 16:58 Walt H
-- strict thread matches above, loose matches on Subject: below --
2003-04-16 14:59 Brien
2003-04-16 16:51 ` Bruce Harada
2003-04-16 20:53 ` Robert White
2003-04-16 21:01 ` Brien
2003-04-16 22:05 ` root
2003-04-17 1:16 ` Mike Dresser
2003-04-17 5:34 ` Peter Svensson
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=200304171241.IAA08069@mc.com \
--to=mbs@mc.com \
--cc=admin@brien.com \
--cc=cfriesen@nortelnetworks.com \
--cc=john@grabjohn.com \
--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