linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nat Makarevitch <nat@makarevitch.org>
To: linux-raid@vger.kernel.org
Subject: Re: the '--setra 65536' mistery, analysis and WTF?
Date: Fri, 21 Mar 2008 15:12:13 +0000 (UTC)	[thread overview]
Message-ID: <loom.20080321T150605-207@post.gmane.org> (raw)
In-Reply-To: 18402.7274.174605.611654@tree.ty.sabi.co.uk

Peter Grandi <pg_lxra <at> lxra.for.sabi.co.UK> writes:

> this seems to indicate that not only the Linux block IO subsystems issues
> IO operations in multiples of the read-ahead size, but does so at a fixed
> number of times per second that is a multiple of 10.

Is it the case with a classic controller (not a 3ware?)

http://forums.storagereview.net/index.php?showtopic=25923 may be of
interest.

> Which lead me to think about elevators, which was also mentioned
> in some recent (and otherwise less interesting :->)

Sorry, I don't understand this.

> It still seems the case to me that the block IO subsystem
> structures IO in lots of read-ahead sectors

Isn't it specific to the 3ware driver and/or hardware, even in
SINGLE (JBOD) mode?

> Finally, I am getting a bit skeptical about elevators in general;

> several tests show no-elevator as not being significantly worse
> and sometimes better than any elevator

Isn't it specific to intelligent controllers?



  reply	other threads:[~2008-03-21 15:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05 17:21 the '--setra 65536' mistery, analysis and WTF? pg_mh, Peter Grandi
2008-03-13 13:02 ` Nat Makarevitch
2008-03-18 21:31 ` Peter Grandi
2008-03-20  8:12   ` Peter Grandi
2008-03-21 15:12     ` Nat Makarevitch [this message]
2008-03-25 12:05 ` Why are MD block IO requests subject to 'plugging'? Peter Grandi
2008-03-25 19:39   ` Peter Grandi
2008-03-27  4:07   ` Neil Brown

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=loom.20080321T150605-207@post.gmane.org \
    --to=nat@makarevitch.org \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).