All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Jeff V. Merkey" <jmerkey@utah-nac.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	"Chen, Kenneth W" <kenneth.w.chen@intel.com>,
	linux-kernel@vger.kernel.org, Jens Axboe <axboe@suse.de>
Subject: Re: kernel performance update - 2.6.14
Date: Sat, 29 Oct 2005 12:49:13 +1000	[thread overview]
Message-ID: <4362E329.8040204@yahoo.com.au> (raw)
In-Reply-To: <4362A9A7.2090101@utah-nac.org>

Jeff V. Merkey wrote:
> 
> Verified.  These numbers reflect my measurements as well.    I have not 
> moved off 2.6.9 to newer kernels on shipping products due to these 
> issues.   There are also serious stability issues as well, though 2.6.14 
> seems a little better than than previous kernels. 
> Jeff
> 

These issues aren't going to fix themselves. Did you investigate
any of the performance or (more importantly) stability problems?

-- 
SUSE Labs, Novell Inc.

Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2005-10-29  2:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-28 23:44 kernel performance update - 2.6.14 Chen, Kenneth W
2005-10-28 23:54 ` Jeff Garzik
2005-10-28 22:43   ` Jeff V. Merkey
2005-10-29  2:49     ` Nick Piggin [this message]
2005-10-29  3:06       ` jmerkey
2005-10-29  3:08         ` jmerkey
2005-10-29  3:15           ` jmerkey
2005-10-29  8:38           ` Nick Piggin
2005-10-29  0:04   ` Chen, Kenneth W
2005-10-29  0:19 ` Felix Oxley
2005-10-29  0:29   ` Felix Oxley
2005-10-29  0:42     ` Chen, Kenneth W
2005-10-29 11:17       ` Dr. David Alan Gilbert
2005-10-29  0:29   ` Chen, Kenneth W
  -- strict thread matches above, loose matches on Subject: below --
2005-11-08  0:04 Chen, Tim C

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=4362E329.8040204@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=axboe@suse.de \
    --cc=jgarzik@pobox.com \
    --cc=jmerkey@utah-nac.org \
    --cc=kenneth.w.chen@intel.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 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.