From: James Bottomley <James.Bottomley@steeleye.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Alan Cox <alan@redhat.com>,
"Salyzyn, Mark" <mark_salyzyn@adaptec.com>,
Arjan van de Ven <arjanv@redhat.com>,
Clay Haapala <chaapala@cisco.com>,
Christoph Hellwig <hch@infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: PATCH: Further aacraid work
Date: 27 Jun 2004 12:33:19 -0500 [thread overview]
Message-ID: <1088357603.10872.69.camel@mulgrave> (raw)
In-Reply-To: <20040618203207.GK1863@holomorphy.com>
On Fri, 2004-06-18 at 15:32, William Lee Irwin III wrote:
> On Fri, Jun 18, 2004 at 08:05:18AM -0700, William Lee Irwin III wrote:
> > Proper changelog this time, and comments, too. Adaptec et al, please
> > verify this resolves the issues you've been having.
> > Someone say _something_.
>
> jejb's seeing such improved results that I don't believe we need to
> wait for Adaptec's ack to merge this.
>
> akpm, please apply.
The patch is already in mainline, but here's my final set of statistics
on it. I traced the effectiveness over a full day's operations on a
scsi build and test machine (I don't get uptime much over a day on these
machines since they're usually being rebooted to test new patches).
The machine is an 8-way p66 voyager with 256k of memory.
I did notice the mergers start off high (at around 50%) after first boot
and then decline. The asymptote of the decline appears to be around 26%
which is still a respectable merge rate for a non-iommu machine. I was
impressed to see that even at the end of the day I was still getting
multi-page merges (still up to 128 pages).
The instrumentation counts the total number of pages in merged segments
and the total number of segments through the machine. The final figures
for the day were
Total pages merged: 192682
Total segments: 549497
So the amount of I/O through the system is 2.2-2.9GB or more than ten
times the machine's actual memory capacity (hopefully this puts me well
up into the usual operating region for physical page fragmentation).
James
next prev parent reply other threads:[~2004-06-27 17:35 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 17:54 PATCH: Further aacraid work Salyzyn, Mark
2004-06-17 20:38 ` Alan Cox
2004-06-17 20:48 ` William Lee Irwin III
2004-06-17 20:56 ` James Bottomley
2004-06-18 15:05 ` William Lee Irwin III
2004-06-18 20:32 ` William Lee Irwin III
2004-06-27 17:33 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-29 20:55 Salyzyn, Mark
2004-06-29 23:22 ` Byron Stanoszek
2004-06-30 19:52 ` Byron Stanoszek
2004-06-30 19:59 ` Dario
2004-06-29 19:27 Salyzyn, Mark
2004-06-29 20:20 ` Byron Stanoszek
2004-06-29 20:42 ` Alan Cox
2004-06-29 18:53 Salyzyn, Mark
2004-06-29 19:03 ` Byron Stanoszek
2004-06-28 13:17 Salyzyn, Mark
2004-06-18 20:53 Salyzyn, Mark
[not found] <286GI-5y3-11@gated-at.bofh.it>
[not found] ` <286Qp-5EU-19@gated-at.bofh.it>
2004-06-17 19:10 ` Andi Kleen
2004-06-17 20:54 ` Alan Cox
2004-06-17 21:13 ` James Bottomley
2004-06-17 21:25 ` Andi Kleen
2004-06-18 15:19 ` Benjamin Herrenschmidt
2004-06-18 5:57 ` Jeff Garzik
2004-06-18 14:07 ` James Bottomley
2004-06-18 15:17 ` Benjamin Herrenschmidt
2004-06-17 14:39 Salyzyn, Mark
2004-06-17 14:55 ` James Bottomley
2004-06-17 14:58 ` Alan Cox
2004-06-17 15:15 ` Arjan van de Ven
2004-06-17 19:16 ` James Bottomley
2004-06-17 16:32 ` Clay Haapala
2004-06-17 16:37 ` James Bottomley
2004-06-17 16:46 ` Alan Cox
2004-06-17 15:11 ` Anton Blanchard
2004-06-17 12:53 Salyzyn, Mark
2004-06-17 13:07 ` Matthew Wilcox
2004-06-17 13:19 ` Christoph Hellwig
2004-06-17 13:55 ` James Bottomley
2004-06-17 13:32 ` Christoph Hellwig
2004-06-17 14:02 ` Alan Cox
2004-06-16 21:04 Alan Cox
2004-06-16 21:33 ` Christoph Hellwig
2004-06-16 21:40 ` Alan Cox
2004-06-16 21:42 ` Christoph Hellwig
2004-06-16 21:48 ` Alan Cox
2004-06-16 21:58 ` Christoph Hellwig
2004-06-16 22:06 ` Alan Cox
2004-06-29 17:48 ` Byron Stanoszek
2004-06-29 18:27 ` Mark Haverkamp
2004-06-29 18:37 ` Alan Cox
2004-06-30 2:02 ` bm
2004-06-30 16:07 ` Alan Cox
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=1088357603.10872.69.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=alan@redhat.com \
--cc=arjanv@redhat.com \
--cc=chaapala@cisco.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
--cc=wli@holomorphy.com \
/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