public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: GrandMasterLee <masterlee@digitalroadkill.net>
To: Andrew Morton <akpm@digeo.com>
Cc: Con Kolivas <conman@kolivas.net>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [BENCHMARK] max bomb segment tuning with read latency 2 patch in  contest
Date: 07 Dec 2002 00:15:01 -0600	[thread overview]
Message-ID: <1039241701.2855.19.camel@localhost> (raw)
In-Reply-To: <3DF18D38.F493636C@digeo.com>

On Fri, 2002-12-06 at 23:55, Andrew Morton wrote:
[...]
> If the SMP machine is using scsi then that tends to make the elevator
> changes less effective.  Because the disk sort-of has its own internal
> elevator which in my testing on a Fujitsu disk has the same ill-advised
> design as the kernel's elevator: it treats reads and writes in a similar
> manner.
> 
> Setting the tag depth to zero helps heaps.

Command tag queue? As in the compile time option? Or do you mean queue
depth?(or are they the same)

> But as you're interested in `desktop responsiveness' you should be
> mostly testing against IDE disks.  Their behavour tends to be quite
> different.
> 
> If you can turn on write caching on the SCSI disks that would change
> the picture too.

Just for clarity, What about for something like FC attached storage
Where the controllers enforce cache policies on a "per volume" basis?
Would that == the same thing? 



--The GrandMaster

  parent reply	other threads:[~2002-12-07  6:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-07  5:20 [BENCHMARK] max bomb segment tuning with read latency 2 patch in contest Con Kolivas
2002-12-07  5:55 ` Andrew Morton
2002-12-07  6:09   ` Con Kolivas
2002-12-07  6:14     ` Andrew Morton
2002-12-07  6:15   ` GrandMasterLee [this message]
2002-12-07  6:20   ` GrandMasterLee
2002-12-07  6:45     ` [BENCHMARK] max bomb segment tuning with read latency 2 patchin contest Andrew Morton
2002-12-07 13:29 ` [BENCHMARK] max bomb segment tuning with read latency 2 patch in contest Con Kolivas
2002-12-10 10:50 ` Miquel van Smoorenburg
2002-12-10 10:55   ` Marc-Christian Petersen

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=1039241701.2855.19.camel@localhost \
    --to=masterlee@digitalroadkill.net \
    --cc=akpm@digeo.com \
    --cc=conman@kolivas.net \
    --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