linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Jens Axboe <axboe@suse.de>
Cc: Andrew Morton <akpm@digeo.com>,
	lkml <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: 2.5.38-mm2
Date: Tue, 24 Sep 2002 17:10:54 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.3.96.1020924170725.19732C-100000@gatekeeper.tmr.com> (raw)
In-Reply-To: <20020923071633.GA15479@suse.de>

On Mon, 23 Sep 2002, Jens Axboe wrote:

> Ah interesting. I do still think that it is worth to investigate _why_
> both elevator_linus and deadline does not prevent the read starvation.
> The read-latency is a hack, not a solution imo.
> 
> >  tagged command queueing on scsi - it appears to be quite stupidly
> >  implemented.
> 
> Ahem I think you are being excessively harsh, or maybe passing judgement
> on something you haven't even looked at. Did you consider that you
> _drive_ may be the broken component? Excessive turn-around times for
> request when using deep tcq is not unusual, by far.

I do think that's what he meant!  I think most drives are optimized this
way, and performance would be better if the kernel used the queueing more
sparingly, so the drive couldn't just run with the writes and let the
reads take the leftovers. 

I think that's a better long run solution, although the fix addresses the
immediate problem.

-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  parent reply	other threads:[~2002-09-24 21:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-23  4:20 2.5.38-mm2 Andrew Morton
2002-09-23  7:16 ` 2.5.38-mm2 Jens Axboe
2002-09-23  7:43   ` 2.5.38-mm2 Andrew Morton
2002-09-24 21:10   ` Bill Davidsen [this message]
2002-09-23  9:45 ` 2.5.38-mm2 [PATCH] Dipankar Sarma
2002-09-23 16:28   ` Andrew Morton
2002-09-23 17:33     ` Dipankar Sarma
2002-09-24  4:41   ` Rusty Russell
2002-09-24 10:24     ` Dipankar Sarma
2002-09-24 14:56       ` Rusty Russell
2002-09-23  9:56 ` 2.5.38-mm2 [PATCH] (dcache) Dipankar Sarma

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=Pine.LNX.3.96.1020924170725.19732C-100000@gatekeeper.tmr.com \
    --to=davidsen@tmr.com \
    --cc=akpm@digeo.com \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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