From: Bob Sanders <rsanders@sgi.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Planning a new box - AMD Opteron or Intel Xeon?
Date: Mon, 12 Nov 2007 08:55:40 -0800 [thread overview]
Message-ID: <20071112165540.GD207902@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0711102320210.26994@penguin.linuxhardware.org>
Kris Kersey (Augustus), mused, then expounded:
> Not to start an argument but from personal experience I have never had a
> problem with NVIDIA or Broadcom chips. Sometimes Marvell has not been as
> good though.
>
To add to Augustus' comment, I've used a lot of Broadcom and Intel network
chips with a number of different linux kernels, and haven't had any real
issues, other than soem unexplained latency differences on nodes in a cluster
with the Intel chips. I haven't had the ability to try the same with the
Broadcom chips, so can't comment on their performance in the same conditions.
That said, Intel just rev'ed their network chips to deal with issues. And the
new chips use the igb driver that's not in older Linux kernels. So just
a head's up.
And at home, my personal system is running an Nvidia chipset with no issues
for my personal usage.
Bob
> Thanks,
> Kris Kersey (Augustus)
> LinuxHardware.org Site Manager
> augustus@linuxhardware.org
> Gentoo Linux AMD64 Developer
> augustus@gentoo.org
> AIM: Augustus22
>
> On Sun, 11 Nov 2007, P.V.Anthony wrote:
>
>> On this day, 10-November-2007 11:11 PM, Conway S. Smith wrote:
>>> I'm in the planning stages of assembling a new box for myself @ home,
>>> and I'm debating if I want to go with AMD Opteron or Intel Xeon. I've
>>> been focusing on Tyan motherboards, as I've heard here on the list that
>>> they've got really excellent Linux (and general) support. In the past
>>> I've mostly gone w/ AMD CPUs, as they had a significantly better
>>> price:performance ratio, but it's been a few years since I last did a
>>> lot of shopping around, and I'm starting to think things may have
>>> changed. I'm still leaning towards AMD Opterons (Barcelona), but I'm
>>> interested in hearing everyone else's opinions.
>>
>> I know that AMD cpus are better but I had some problems with the onboard
>> network chips. Most of the motherboards come with some Marvell, Broadcom
>> or Nvidia network chips and these chips did not work for me.
>>
>> I choose Intel chipset motherboards with Intel network because their
>> network cards are really good.
>>
>> The drivers in the kernel are really good for me.
>>
>> P.V.Anthony
>> --
>> gentoo-amd64@gentoo.org mailing list
>>
>>
>>
> --
> gentoo-amd64@gentoo.org mailing list
>
--
-
--
gentoo-amd64@gentoo.org mailing list
prev parent reply other threads:[~2007-11-12 16:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 15:11 [gentoo-amd64] Planning a new box - AMD Opteron or Intel Xeon? Conway S. Smith
2007-11-10 16:28 ` Kris Kersey (Augustus)
2007-11-10 16:52 ` Conway S. Smith
2007-11-10 17:43 ` Beso
2007-11-11 12:38 ` Conway S. Smith
2007-11-11 13:23 ` Beso
2007-11-12 1:43 ` [gentoo-amd64] " Duncan
2007-11-12 2:55 ` Conway S. Smith
2007-11-12 17:42 ` [gentoo-amd64] " Bob Sanders
2007-11-10 23:20 ` Kris Kersey (Augustus)
2007-11-11 14:03 ` Bernhard Auzinger
2007-11-12 1:50 ` Richard Freeman
2007-11-12 14:39 ` Kris Kersey (Augustus)
2007-11-10 17:22 ` P.V.Anthony
2007-11-10 23:21 ` Kris Kersey (Augustus)
2007-11-12 16:55 ` Bob Sanders [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=20071112165540.GD207902@sgi.com \
--to=rsanders@sgi.com \
--cc=gentoo-amd64@lists.gentoo.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