mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthias Andree <matthias.andree@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: IDE TCQ
Date: Sat, 16 Nov 2002 01:16:41 +0100	[thread overview]
Message-ID: <20021116001641.GD26188@merlin.emma.line.org> (raw)
In-Reply-To: <20021113113940.GE832@suse.de>

On Wed, 13 Nov 2002, Jens Axboe wrote:

> > Second set of questions: Does it do any good to one-channel-one-disk
> > setups?  Is it supposed to do good to access time, operations/sec,
> > throughput, random reqs rearrangement or what?  Do you have any
> > figures how much TCQ helps performace (e.g. in file serving case)?
> 
> Yes it will help any setup. Due to way ide tcq works, it's recommended
> only to use tcq on one drive on a channel right now. This may change in
> the future.

Would be "it's recommended to use only one drive on a channel for best
results, whether with or without TCQ" more accurate? Or are there
reasons that make TCQ <-> slave interactions particularly bad that don't
show up without TCQ?

> I don't have any general numbers. I did some benchmarking when I first
> implemented it, and it typically shows (as with scsi drives) that having
> just enough tags to keep the disk busy helps a bit. The linux io
> scheduler does the rest. For random reads, 10-30% speed increase was
> observed.

Did you perchance benchmark the impact TCQ has on sequential writes when
the write cache is turned off?

Turning off the write cache without TCQ has a severe impact (30 to 70%
on my "stupid dd" tests) in my computer (VIA82C686, but I don't recall
which drive I did this on, it was either of IBM DJNA, DTLA or Maxtor
4W060H4)

      reply	other threads:[~2002-11-16  0:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-12 17:46 Sasi Péter
2002-11-13 11:39 ` Jens Axboe
2002-11-16  0:16   ` Matthias Andree [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=20021116001641.GD26188@merlin.emma.line.org \
    --to=matthias.andree@gmx.de \
    --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

all inboxes | Powered by JetHome®