public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel performance update - 2.6.14
Date: Sat, 29 Oct 2005 12:17:48 +0100	[thread overview]
Message-ID: <20051029111748.GA6074@gallifrey> (raw)
In-Reply-To: <200510290042.j9T0gsg28096@unix-os.sc.intel.com>

Hi,
  Have you any idea what happened to cpu-fp on the Dual Xeons?
Accross the other 2 platforms it is pretty stable, but cpu-fp
seems to have gone up a few % around 2.6.13-rc7 and dropped back
down around 2.6.1.4-rc2 and 2.6.14-rc4; now it isn't any lower
than where you started - but it would be nice to have whatever
it was that got that extra few %.

Dave
--
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    | Running GNU/Linux on Alpha,68K| Happy  \ 
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

  reply	other threads:[~2005-10-29 11:17 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
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 [this message]
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=20051029111748.GA6074@gallifrey \
    --to=linux@treblig.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox