linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Hardy <mhardy@h3c.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH md 2 of 4] Fix raid6 problem
Date: Sun, 13 Feb 2005 14:58:50 -0800	[thread overview]
Message-ID: <420FDBAA.4010005@h3c.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0502131602470.16537-100000@coffee.psychology.mcmaster.ca>



Mark Hahn wrote:
>>Interesting - the private mail was from me, and I've got two dual 
>>Opterons in service. The one with significantly more PCI activity has 
>>significantly more problems then the one with less PCI activity.
> 
> 
> that's pretty odd, since the most intense IO devices I know of 
> are cluster interconnect (quadrics, myrinet, infiniband),
> and those vendors *love* opterons.  I've never heard any of them
> say other than that Opteron IO handling is noticably better than
> Intel's.

Sure, but which variables are changed between the rigs the vendors 
loved, and the rig we're having problems with?

> otoh, I could easily believe that if you're running the Opteron 
> systems in acts-like-a-faster-xeon mode (ie, not x86_64),
> you might be exercising some less-tested paths.

Its running x86_64 (Fedora Core 3) and the problem is rooted in the 
chipset I believe. I don't think its Opterons per se, I think its just 
the Athlon take two - which is to say that its a wonderful chip, but 
some of the chipsets its saddled with are horrible, and careful 
selection (as well as heavy testing prior to putting a machine in 
service) is essential.

-Mike

  parent reply	other threads:[~2005-02-13 22:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200502031145.j13Bj1fl016074@terminus.zytor.com>
2005-02-03 16:39 ` [PATCH md 2 of 4] Fix raid6 problem H. Peter Anvin
2005-02-03 16:59   ` Lars Marowsky-Bree
2005-02-03 17:06     ` H. Peter Anvin
2005-02-03 17:43   ` Guy
2005-02-03 18:07     ` H. Peter Anvin
2005-02-03 19:36       ` Gordon Henderson
2005-02-04  9:04         ` Andrew Walrond
2005-02-04 11:19           ` Gordon Henderson
2005-02-04 18:31             ` Mike Hardy
2005-02-13 21:05               ` Mark Hahn
2005-02-13 21:19                 ` Gordon Henderson
2005-02-14  4:56                   ` Tim Moore
2005-02-14  9:42                     ` Andrew Walrond
2005-02-13 22:58                 ` Mike Hardy [this message]
2005-02-13 23:14                   ` Richard Scobie
2005-02-06  3:38             ` Tim Moore
2005-02-14  4:49             ` Tim Moore
2005-02-14  8:09               ` Gordon Henderson
2005-02-14  4:27         ` Tim Moore
2005-02-14  8:05           ` Gordon Henderson
2004-11-03 23:56 A. James Lewis
2004-12-09  0:21 ` H. Peter Anvin
2004-12-09  0:35   ` Jim Paris
     [not found] ` <200412090021.iB90L4MK014200@terminus.zytor.com>
2005-01-23 14:02   ` A. James Lewis
2005-01-23 14:42     ` Kevin P. Fleming
2005-02-03  2:12     ` H. Peter Anvin
2005-02-03 17:13       ` Andy Smith
  -- strict thread matches above, loose matches on Subject: below --
2004-11-02  3:37 [PATCH md 0 of 4] Introduction NeilBrown
2004-11-02  3:37 ` [PATCH md 2 of 4] Fix raid6 problem NeilBrown

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=420FDBAA.4010005@h3c.com \
    --to=mhardy@h3c.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).