X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7F702.DE259E22@onstor-exch02.onstor.net>; Fri, 14 Sep 2007 11:10:09 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Free BSD for Yahoo test
Date: Fri, 14 Sep 2007 11:10:08 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0587B3B0@onstor-exch02.onstor.net>
In-Reply-To: <20070914110659.15d9dccc@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Free BSD for Yahoo test
Thread-Index: Acf2+gyUd1t4sQfjSseaQUL+urJtowAB+NmQ
From: "Eric Barrett" <eric.barrett@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "John Rogers" <john.rogers@onstor.com>,
	"Brian Montero" <brian.montero@onstor.com>,
	"Fay Chong" <fay.chong@onstor.com>,
	"Paul Hammer" <paul.hammer@onstor.com>,
	"Brian Baker" <brian.baker@onstor.com>,
	"Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>,
	"Brian DeForest" <brian.deforest@onstor.com>

> Please don't group this week's Redhat intern charged with putting
> together a kernel with a Debian kernel package maintainer.  Also try
to
> remember that a distro isn't a kernel and vice versa.  I run Debian
but
> I don't run one of their kernels.  So this isn't a distro-centric
issue.

I've been using Linux since the 0.99 kernels and Slackware 1.1, so I'm
well aware that a kernel and distro aren't the same.  My point was that
no major distro out there uses the stock kernel.org code out of the box.

> > A good example of how badly kernels can break -- we installed stock
> > Linux 2.6.22 on beast (the data warehouse system) and dd performance
> > dropped from 110MB/sec to 2.  Yes, two.
>
> Doesn't imply a breakage in the kernel.  More like a breakage in our
> filer.  Although maybe your implication that Trondie is slipping in
> some NFS code that would give competitors a headache is always
possible.

Well, I tried it against a Solaris NFS server and got the same results.
Since I was rebooting a production machine to troubleshoot, I stopped
when
I got it working again, so I never did track down what the problem was
or
where, precisely, it broke.  It might have even been in the network or
(Ethernet) driver layer.

Also, Trond wouldn't do something like that, and I didn't mean to imply
that he would.  Maybe you were joking, though, and my joke meter is just
broken.
