From: Sonny Rao <sonny@burdell.org>
To: Anton Blanchard <anton@samba.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-rc1-mm1
Date: Mon, 19 Sep 2005 16:01:36 -0400 [thread overview]
Message-ID: <20050919200136.GA22144@kevlar.burdell.org> (raw)
In-Reply-To: <20050916205517.GA8638@kevlar.burdell.org>
On Fri, Sep 16, 2005 at 04:55:17PM -0400, Sonny Rao wrote:
> On Fri, Sep 16, 2005 at 08:17:00PM +1000, Anton Blanchard wrote:
> > On Fri, Sep 16, 2005 at 02:23:19AM -0700, Andrew Morton wrote:
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc1/2.6.14-rc1-mm1/
> >
> > Builds and boots on ppc64 (POWER5) with the following patch, I forgot to
> > include siginfo.h when I added data breakpoint support. We must include
> > it in a round-a-bout way in mainline.
>
> Excellent, now I'm about to start up perf testing on 2.6.14-rc1-mm1
>
> with and without the following patches:
>
> mm-try-to-allocate-higher-order-pages-in-rmqueue_bulk.patch
> mm: try to allocate higher order pages in rmqueue_bulk
>
> mm-try-to-allocate-higher-order-pages-in-rmqueue_bulk-fix.patch
> mm-try-to-allocate-higher-order-pages-in-rmqueue_bulk fix
>
> mm-page_alloc-increase-size-of-per-cpu-pages.patch
> mm: page_alloc: increase size of per-cpu-pages
>
> mm-set-per-cpu-pages-lower-threshold-to-zero.patch
> mm: set per-cpu-pages lower threshold to zero
>
Here are the results:
bench 2.6.14-rc1-mm1 2.6.14-rc1-mm1-revert
-- -- --
kernbench 438.88 sec 439.49 sec 0.1 % slower
dbench3 (16) 1089.14 MB/sec 1062.89 MB/sec 2.5 % slower
dbench3 was run on a tmpfs
To avoid certain issues, SDET is given in relative terms.
sdet (64) 100 % 100.2 %
next prev parent reply other threads:[~2005-09-19 20:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 9:23 2.6.14-rc1-mm1 Andrew Morton
2005-09-16 9:45 ` 2.6.14-rc1-mm1 Pekka Enberg
2005-09-16 10:17 ` 2.6.14-rc1-mm1 Anton Blanchard
2005-09-16 20:55 ` 2.6.14-rc1-mm1 Sonny Rao
2005-09-19 20:01 ` Sonny Rao [this message]
2005-09-16 12:20 ` [PATCH] drivers/base: a little speedup and cleanup Jiri Slaby
2005-09-16 15:48 ` Dmitry Torokhov
2005-09-16 17:49 ` 2.6.14-rc1-mm1 Serge E. Hallyn
2005-09-16 18:41 ` 2.6.14-rc1-mm1 Dominik Karall
2005-09-16 19:46 ` 2.6.14-rc1-mm1 Jiri Slaby
2005-09-16 19:59 ` 2.6.14-rc1-mm1 Kay Sievers
2005-09-16 20:04 ` 2.6.14-rc1-mm1 Jiri Slaby
2005-09-16 21:30 ` 2.6.14-rc1-mm1 Greg KH
2005-09-16 23:53 ` 2.6.14-rc1-mm1 Valdis.Kletnieks
2005-09-17 0:10 ` 2.6.14-rc1-mm1 Greg KH
2005-09-17 1:18 ` 2.6.14-rc1-mm1 Dr.Dre
2005-09-17 1:29 ` 2.6.14-rc1-mm1 Kay Sievers
2005-09-17 0:15 ` 2.6.14-rc1-mm1 Andrew Morton
2005-09-17 4:09 ` 2.6.14-rc1-mm1 Valdis.Kletnieks
2005-09-17 1:22 ` 2.6.14-rc1-mm1 Avuton Olrich
2005-09-17 4:41 ` 2.6.14-rc1-mm1 Andrew Morton
2005-09-17 10:10 ` 2.6.14-rc1-mm1 Neil Brown
2005-09-17 1:51 ` 2.6.14-rc1-mm1 Martin J. Bligh
2005-09-17 4:22 ` 2.6.14-rc1-mm1 Martin J. Bligh
2005-09-17 4:25 ` [PATCH] mips: Fixed build error Yoichi Yuasa
2005-09-17 4:33 ` Andrew Morton
2005-09-17 5:27 ` Yoichi Yuasa
2005-09-20 22:42 ` one more oops on sensor modules removal J.A. Magallon
2005-09-21 5:56 ` Andrew Morton
2005-09-21 8:52 ` Grant Coady
2005-10-01 11:39 ` Jean Delvare
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=20050919200136.GA22144@kevlar.burdell.org \
--to=sonny@burdell.org \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--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
all inboxes | Powered by JetHome®