Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Brad Campbell <lists2009@fnarfbargle.com>
To: Wols Lists <antlists@youngman.org.uk>
Cc: linux-raid@vger.kernel.org
Subject: Re: Implementing Global Parity Codes
Date: Tue, 30 Jan 2018 22:18:34 +0800	[thread overview]
Message-ID: <867daa46-ac15-a0a2-8809-89af882ad3a4@fnarfbargle.com> (raw)
In-Reply-To: <5A6F5D9B.5060201@youngman.org.uk>

On 30/01/18 01:44, Wols Lists wrote:

> Except that most drives don't do that nowadays, they do "constant linear
> velocity" so the drive speeds up or slows down depending on where the
> heads are, I believe.

No. Hard disks have one speed. That can be easily proven by popping the 
top off and putting a tacho on the spindle, or just looking at any 
linear read benchmark as they all demonstrate that data transfer slows 
down as the head works its way towards the spindle.

Same reason the first couple of tracks on each LP sounded better. More 
vinyl to get a better response.

Optical disks used CLV where they needed to get bits out at a specific 
clock rate (ie Audio).

Brad.

  parent reply	other threads:[~2018-01-30 14:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-27  5:47 Implementing Global Parity Codes mostafa kishani
2018-01-27  8:37 ` Wols Lists
2018-01-27 14:29   ` mostafa kishani
2018-01-27 15:13     ` Wols Lists
2018-01-28 13:00       ` mostafa kishani
2018-01-29 10:22       ` David Brown
2018-01-29 17:44         ` Wols Lists
2018-01-30 11:47           ` David Brown
2018-01-30 14:18           ` Brad Campbell [this message]
2018-01-30 11:30         ` mostafa kishani
2018-01-30 15:14           ` David Brown
2018-01-31 16:03             ` mostafa kishani
2018-01-31 17:53               ` Piergiorgio Sartor
2018-02-02  5:24 ` NeilBrown
2018-02-03  6:01   ` mostafa kishani

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=867daa46-ac15-a0a2-8809-89af882ad3a4@fnarfbargle.com \
    --to=lists2009@fnarfbargle.com \
    --cc=antlists@youngman.org.uk \
    --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