public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Stephen Lord <lord@sgi.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: SCSI I/O performance problems when CONFIG_HIGHIO is off
Date: Mon, 18 Nov 2002 15:12:37 +0100	[thread overview]
Message-ID: <20021118141237.GA1024@suse.de> (raw)
In-Reply-To: <1037628312.1680.5.camel@laptop.americas.sgi.com>

On Mon, Nov 18 2002, Stephen Lord wrote:
> On Mon, 2002-11-18 at 06:05, Jens Axboe wrote:
> 
> > 
> > Steve,
> > 
> > Something isn't quite making sense. If we go over every single instance
> > of checking ->highmem_io, they all look sane (ie checking on non-highmem
> > setup must yield 0). So that part looks good.
> > 
> > However, I think a typo snuck in there, in exactly the spot you pasted
> > above. Could you try 2.4.20-rc2 with this patch applied?
> > 
> > ===== drivers/scsi/scsi_merge.c 1.9 vs edited =====
> > --- 1.9/drivers/scsi/scsi_merge.c	Mon Sep 16 09:25:10 2002
> > +++ edited/drivers/scsi/scsi_merge.c	Mon Nov 18 13:04:41 2002
> > @@ -835,7 +835,7 @@
> >  	 * case.
> >   	 */
> >  	if (count == 1 && !SCpnt->host->highmem_io) {
> > -		this_count = req->current_nr_sectors;
> > +		this_count = req->nr_sectors;
> >  		goto single_segment;
> >  	}
> 
> That looks like it does it, performance is pretty much what I was
> getting with HIGHIO on.

Great, thanks for verifying that. I'll push it to Marcelo ASAP.

-- 
Jens Axboe


      reply	other threads:[~2002-11-18 14:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-15 20:31 SCSI I/O performance problems when CONFIG_HIGHIO is off Steve Lord
2002-11-16  8:18 ` Jens Axboe
2002-11-18 12:05 ` Jens Axboe
2002-11-18 14:05   ` Stephen Lord
2002-11-18 14:12     ` Jens Axboe [this message]

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=20021118141237.GA1024@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lord@sgi.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