mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "Måns Rullgård" <mru@kth.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: File system compression, not at the block layer
Date: Fri, 23 Apr 2004 16:59:02 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0404231651120.1643@chaos> (raw)
In-Reply-To: <yw1xoepio24x.fsf@kth.se>

On Fri, 23 Apr 2004, [iso-8859-1] Måns Rullgård wrote:

> "Richard B. Johnson" <root@chaos.analogic.com> writes:
>
> > On Fri, 23 Apr 2004, Joel Jaeggli wrote:
> >
> >> On Fri, 23 Apr 2004, Paul Jackson wrote:
> >>
> >> > > SO... in addition to the brilliance of AS, is there anything else that
> >> > > can be done (using compression or something else) which could aid in
> >> > > reducing seek time?
> >> >
> >> > Buy more disks and only use a small portion of each for all but the
> >> > most infrequently accessed data.
> >>
> >> faster drives. The biggest disks at this point are far slower that the
> >> fastest... the average read service time on a maxtor atlas 15k is like
> >> 5.7ms on 250GB western digital sata, 14.1ms, so that more than twice as
> >> many reads can be executed on the fastest disks you can buy now... of
> >> course then you pay for it in cost, heat, density, and controller costs.
> >> everthing is a tradeoff though.
> >>
> >
> > If you want to have fast disks, then you should do what I
> > suggested to Digital 20 years ago when they had ST-506
> > interfaces and SCSI was available only from third-parties.
> > It was called "striping" (I'm serious!). Not the so-called
> > RAID crap that took the original idea and destroyed it.
> > If you have 32-bits, you design an interface board for 32
> > disks. The interface board strips each bit to the data that
> > each disk gets. That makes the whole array 32 times faster
> > than a single drive and, of course, 32 times larger.
>
> For best performance, the spindles should be synchronized too.  This
> might be tricky with disks not intended for such operation, of course.

Actually not. You need a FIFO to cache your bits into buffers of bytes
anyway. Depending upon the length of the FIFO, you can "rubber-band" a
lot of rotational latency. When you are dealing with a lot of drives,
you are never going to have all the write currents turn on at the same
time anyway because they are (very) soft-sectored, i.e., block
replacement, etc.

Your argument was used to shout down the idea. Actually, I think
it was lost in the NIH syndrome anyway.

>
> --
> Måns Rullgård
> mru@kth.se
>


Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5557.45 BogoMips).
            Note 96.31% of all statistics are fiction.



  reply	other threads:[~2004-04-23 20:58 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23 17:26 Timothy Miller
2004-04-23 17:30 ` Miquel van Smoorenburg
2004-04-23 17:41   ` Theodore Ts'o
2004-04-23 17:57     ` Jörn Engel
2004-04-23 18:14     ` Timothy Miller
2004-04-23 18:34       ` Paul Jackson
2004-04-23 20:14         ` Joel Jaeggli
2004-04-23 20:34           ` Richard B. Johnson
2004-04-23 20:44             ` Måns Rullgård
2004-04-23 20:59               ` Richard B. Johnson [this message]
2004-04-23 21:14                 ` Ben Greear
2004-04-23 21:25                   ` Timothy Miller
2004-04-24  4:58                     ` Ben Greear
2004-04-27 15:45                       ` Timothy Miller
2004-04-23 21:18                 ` Timothy Miller
2004-04-24  1:28                   ` Horst von Brand
2004-04-24  2:24                   ` Tom Vier
2004-04-24  7:36                     ` Willy Tarreau
2004-04-24 16:02                       ` Eric D. Mudama
2004-04-25  3:05                       ` Horst von Brand
2004-04-25  7:29                         ` Willy Tarreau
2004-04-25 19:50                           ` Eric D. Mudama
2004-04-27 15:43                     ` Timothy Miller
2004-04-28  0:29                       ` Tom Vier
2004-04-23 21:31             ` Joel Jaeggli
2004-04-23 22:20               ` Ian Stirling
2004-04-23 23:34             ` Paul Jackson
2004-04-27 15:42               ` Timothy Miller
2004-04-27 16:02                 ` Jörn Engel
2004-04-24  1:18             ` Horst von Brand
2004-04-26 10:22             ` Jörn Engel
2004-04-23 21:15           ` Timothy Miller
2004-04-23 21:36             ` Joel Jaeggli
2004-04-27 20:34     ` Pavel Machek
2004-04-28 22:57       ` Timothy Miller
2004-04-29  9:46         ` Jörn Engel
2004-04-29  9:52           ` Pavel Machek
2004-04-29 10:09             ` Jörn Engel
2004-04-29 10:19               ` Pavel Machek
2004-04-29 17:17             ` Tim Connors
2004-04-28  1:00 ` David Lang
2004-04-28 10:09   ` Jörn Engel
2004-04-28 10:21     ` Nikita Danilov

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=Pine.LNX.4.53.0404231651120.1643@chaos \
    --to=root@chaos.analogic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mru@kth.se \
    /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®