public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Boszormenyi Zoltan <zboszor@externet.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Jens Axboe's blk-11 causing problems
Date: Fri, 24 Nov 2000 21:59:33 +0100	[thread overview]
Message-ID: <20001124215933.H11366@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.02.10011240902070.4804-100000@prins.externet.hu>
In-Reply-To: <Pine.LNX.4.02.10011240902070.4804-100000@prins.externet.hu>; from zboszor@externet.hu on Fri, Nov 24, 2000 at 09:10:22AM +0100

[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]

On Fri, Nov 24 2000, Boszormenyi Zoltan wrote:
> Hi!
> 
> I tried 2.4.0-test11 (plain, +ac1/2) with and without
> Jens' blk-11 patch. This indeed performs (much) better
> when there is only high disk activity but cdrecord
> starts up _very_ slowly if the kernel was compiled with 
> blk-11. It does not happen if blk-11 is not applied.
> 
> I stopped cdrecord before it started writing because of
> this suspicious slowness and I did not want to create a bad CD.
> 
> Other data points:
> The CD-writer is a Yamaha-6416 (SCSI version).
> The SCSI card is a Diamond Fireport-40 (Symbios 53c875j)
> I tested both the in-kernel 1.6b and 1.7.2 versions of the
> sym53c8xx driver.
> 
> The slowdown was experienced in every case where
> the kernel contained blk-11.

You might want to send messages such as this one to me
as well, so I don't miss them :-)

The problem is due to sg assuming that scsi_do_req will
fire the request queue immediately to let the command
inject complete. This was never really the case, even
in the stock kernel. Here's a quick-and-dirty patch
against test11+blk-11 attached, untested but it should
fix the delays.

-- 
* Jens Axboe <axboe@suse.de>
* SuSE Labs

[-- Attachment #2: blk-11-sg-1 --]
[-- Type: text/plain, Size: 399 bytes --]

--- /opt/kernel/linux-2.4.0-test11/drivers/scsi/sg.c	Tue Oct 24 22:58:20 2000
+++ drivers/scsi/sg.c	Fri Nov 24 21:57:50 2000
@@ -689,6 +689,7 @@
 		(void *)SRpnt->sr_buffer, hp->dxfer_len,
 		sg_cmd_done_bh, timeout, SG_DEFAULT_RETRIES);
     /* dxfer_len overwrites SRpnt->sr_bufflen, hence need for b_malloc_len */
+    generic_unplug_device(&SRpnt->sr_device->request_queue);
     return 0;
 }
 

      reply	other threads:[~2000-11-24 21:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-24  8:10 Jens Axboe's blk-11 causing problems Boszormenyi Zoltan
2000-11-24 20:59 ` 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=20001124215933.H11366@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zboszor@externet.hu \
    /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