From: Billy Crook <billycrook@gmail.com>
To: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Stupid question regarding RAID-1 access pattern
Date: Wed, 6 Jan 2010 16:13:55 -0600 [thread overview]
Message-ID: <a43edf1b1001061413p6d3689f0u9be7bc35c8892cd5@mail.gmail.com> (raw)
In-Reply-To: <20100106213723.GA12318@cthulhu.home.robinhill.me.uk>
On Wed, Jan 6, 2010 at 15:37, Robin Hill <robin@robinhill.me.uk> wrote:
> I doubt this would help much really. If you're reading sequential data
> then it's pretty much as quick to keep reading as to seek to the next
> chunk.
Could it hurt [performance]? SSDs will only become more common, and
they haven't any seek penalty.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-01-06 22:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 19:58 Stupid question regarding RAID-1 access pattern Curt Hartung
2010-01-06 21:37 ` Robin Hill
2010-01-06 22:13 ` Billy Crook [this message]
2010-01-06 23:10 ` Robin Hill
2010-01-21 7:34 ` Erno Kuusela
2010-01-21 8:09 ` Asdo
2010-01-07 15:17 ` Leslie Rhorer
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=a43edf1b1001061413p6d3689f0u9be7bc35c8892cd5@mail.gmail.com \
--to=billycrook@gmail.com \
--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).