From: Jens Axboe <axboe@suse.de>
To: Christoph Rohland <cr@sap.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@redhat.com>
Subject: Re: [patch] zero-bounce block highmem I/O, #13
Date: Tue, 28 Aug 2001 14:43:26 +0200 [thread overview]
Message-ID: <20010828144326.R642@suse.de> (raw)
In-Reply-To: <20010827123700.B1092@suse.de> <m3itf85vlr.fsf@linux.local> <20010828125520.L642@suse.de> <20010828134141.M642@suse.de> <m3ae0k5qic.fsf@linux.local>
In-Reply-To: <m3ae0k5qic.fsf@linux.local>
On Tue, Aug 28 2001, Christoph Rohland wrote:
> Hi Jens,
>
> On Tue, 28 Aug 2001, Jens Axboe wrote:
> > Ok found the bug -- SCSI was accidentally using blk_seg_merge_ok
> > when it just wanted to test if we were crossing a 4GB physical
> > address boundary or not. Doh! Attached incremental patch should fix
> > the SCSI performance issue. I'm testing right now...
>
> Yup, performance is back to 2.4.9 level. But I do not see an
> improvement.
>
> I will now do a database import.
Of course it depends on the type of work load how big an improvement you
see. How much RAM is in the machine?
It would be interesting to see profiles of stock + highmem kernels.
--
Jens Axboe
next prev parent reply other threads:[~2001-08-28 12:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 10:37 [patch] zero-bounce block highmem I/O, #13 Jens Axboe
2001-08-28 10:26 ` Christoph Rohland
2001-08-28 10:41 ` Jens Axboe
2001-08-28 10:55 ` Jens Axboe
2001-08-28 11:41 ` Jens Axboe
2001-08-28 12:16 ` Christoph Rohland
2001-08-28 12:43 ` Jens Axboe [this message]
2001-08-28 15:59 ` Christoph Rohland
[not found] ` <m3elpw5smc.fsf@linux.local>
2001-08-28 11:45 ` 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=20010828144326.R642@suse.de \
--to=axboe@suse.de \
--cc=cr@sap.com \
--cc=davem@redhat.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