All of
 help / color / mirror / Atom feed
From: Bron Gondwana <>
To: Bron Gondwana <>
Cc: Adrian Bunk <>,
Subject: Re: Linux
Date: Tue, 8 May 2007 10:08:28 +1000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Feb 12, 2007 at 05:13:47PM +1100, Bron Gondwana wrote:
> On Sat, Feb 10, 2007 at 05:41:13PM +0100, Adrian Bunk wrote:
> > New drivers since
> > - Areca ARC11X0/ARC12X0 SATA-RAID support
> > - AMD Athlon64/FX and Opteron temperature sensor
> Sorry - I think I just sent a blank reply to this!  Oops.
> I was going to say - thanks.  We'll definitely be using
> this kernel since we've found that has a
> significantly worse IO profile and either the
> kernel or 2.6.18 on otherwise identical machines with pretty
> stable loads (so we can compare back to previous weeks).
> Now to figure out what's causing the extra load in the
> 2.6.19 branch!

By the way, we've just tried a kernel on another machine
and so far (fingers crossed) we're not seeing the load issues we
had with the 2.6.19 kernel we were using.

Given that the Areca driver is the same in both, the only other funky
thing we did was a single patch to ReiserFS, but we're applying that
same patch on 2.6.20.

(my sneaking suspicion was that the delayed bitmap loading was to blame,
but it's hard to test these things short of multiple reboots, and we
don't have a testing Cyrus install that we can load that heavily)

Anyway - if this goes well for the next couple of days we'll probably
stop tracking the 2.6.16 series.  Thanks again, very much, for your work
with 2.6.16.  It was fantastic to have this resource to keep us from
having to chase more recent kernels just to get the patches we needed!


      reply	other threads:[~2007-05-08  0:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-10 16:41 Linux Adrian Bunk
2007-02-12  6:12 ` Bron Gondwana
2007-02-12  6:13 ` Bron Gondwana
2007-05-08  0:08   ` Bron Gondwana [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:

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

  git send-email \ \ \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.