From: James Bottomley <James.Bottomley@steeleye.com>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Andi Kleen <ak@suse.de>,
davem@redhat.com, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jens Axboe <axboe@suse.de>,
suparna@in.ibm.com, Linux Kernel <linux-kernel@vger.kernel.org>,
alex_williamson@hp.com, bjorn_helgaas@hp.com
Subject: Re: [RFC] block layer support for DMA IOMMU bypass mode II
Date: 30 Jul 2003 09:20:52 -0500 [thread overview]
Message-ID: <1059574857.1849.7.camel@mulgrave> (raw)
In-Reply-To: <20030730044256.GA1974@dsl2.external.hp.com>
On Tue, 2003-07-29 at 23:42, Grant Grundler wrote:
> On Mon, Jul 28, 2003 at 01:15:13PM +0200, Andi Kleen wrote:
> > Run it with 100-500 users (reaim -f workfile... -s 100 -e 500 -i 100)
>
> jejb was wondering if 4k pages would cause different behaviors becuase
> of file system vs page size (4k vs 16k). ia64 uses 16k by default.
> I've rebuilt the kernel with 4k page size and VMERGE != 0.
> The substantially worse performance feels like a rat hole because
> of 4x pressure on CPU TLB.
OK, I admit it, it was a rat hole. Provided reaim uses large files, we
should only get block<->page fragmentation at the edges, and obviously,
reaim has to use large files otherwise it's not testing the virtual
merging properly...
James
next prev parent reply other threads:[~2003-07-30 14:26 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 16:46 [RFC] block layer support for DMA IOMMU bypass mode James Bottomley
2003-07-01 17:09 ` Andi Kleen
2003-07-01 17:28 ` James Bottomley
2003-07-01 17:42 ` Andi Kleen
2003-07-01 19:22 ` Grant Grundler
2003-07-01 19:56 ` James Bottomley
2003-07-01 17:54 ` H. Peter Anvin
2003-07-01 19:19 ` Grant Grundler
2003-07-01 19:59 ` Alex Williamson
2003-07-01 20:11 ` James Bottomley
2003-07-01 20:03 ` James Bottomley
2003-07-01 23:01 ` Grant Grundler
2003-07-02 15:52 ` James Bottomley
2003-07-01 22:51 ` David S. Miller
2003-07-01 23:57 ` [RFC] block layer support for DMA IOMMU bypass mode II Andi Kleen
2003-07-02 0:03 ` David S. Miller
2003-07-02 0:22 ` Andi Kleen
2003-07-02 0:21 ` David S. Miller
2003-07-02 16:53 ` Grant Grundler
2003-07-02 17:19 ` Andi Kleen
2003-07-02 16:55 ` Grant Grundler
2003-07-02 17:20 ` Andi Kleen
2003-07-02 17:37 ` Grant Grundler
2003-07-02 21:16 ` Alan Cox
2003-07-02 23:56 ` Andi Kleen
2003-07-03 20:26 ` Alan Cox
2003-07-03 21:24 ` Andi Kleen
2003-07-03 22:19 ` Grant Grundler
2003-07-08 2:14 ` David S. Miller
2003-07-08 19:34 ` Andi Kleen
2003-07-08 19:47 ` Jeff Garzik
2003-07-08 20:10 ` Andi Kleen
2003-07-08 20:11 ` Grant Grundler
2003-07-08 22:04 ` David S. Miller
2003-07-08 22:25 ` Grant Grundler
2003-07-08 22:23 ` David S. Miller
2003-07-09 18:55 ` Andi Kleen
2003-07-23 11:40 ` Grant Grundler
2003-07-28 11:15 ` Andi Kleen
2003-07-28 14:59 ` Grant Grundler
2003-07-30 2:31 ` Grant Grundler
2003-08-01 21:51 ` Cliff White
2003-08-01 23:18 ` reaim now available as osdl-aim-7 - " Cliff White
2003-07-30 4:42 ` Grant Grundler
2003-07-30 4:51 ` David S. Miller
2003-07-30 13:06 ` Grant Grundler
2003-07-30 16:02 ` Grant Grundler
2003-07-30 16:36 ` Andi Kleen
2003-07-30 17:18 ` James Bottomley
2003-07-30 14:20 ` James Bottomley [this message]
2003-07-23 13:20 ` Grant Grundler
2003-07-23 15:30 ` Jens Axboe
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=1059574857.1849.7.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alex_williamson@hp.com \
--cc=axboe@suse.de \
--cc=bjorn_helgaas@hp.com \
--cc=davem@redhat.com \
--cc=grundler@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suparna@in.ibm.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 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.