public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Tony Battersby <tonyb@cybernetics.com>
Cc: 'ael' <law_ence.dev@ntlworld.com>, linux-scsi@vger.kernel.org
Subject: Re: st.c block limits
Date: Thu, 1 Aug 2002 17:49:46 +0200 (MEST)	[thread overview]
Message-ID: <200208011549.RAA05274@cave.bitwizard.nl> (raw)
In-Reply-To: <002001c2395d$6e842150$e0019d89@cybernetics.com> from Tony Battersby at "Aug 1, 2002 09:14:55 am"

Tony Battersby wrote:
[Charset iso-8859-1 unsupported, filtering to ASCII...]
> > >># tar -cf /dev/ntape blah_home.tar.bz2; mt  tell
> 
> > The tape has a real 10GB capacity. (I believe.)  The 20BG
> > blocks is correct
> > for the default block size of 512. So compression is not an
> > issue here. And
> > the report above is actually 17.8/2 = 8.9 GB :-(
> 
> Some compression algorithms will actually expand data by a significant
> amount.  For example, many implementations of ALDC compression will give a
> compression ratio of 0.8 on random data.  In your example above you are
> writing a .bz2 file (which is already compressed), so it would probably
> expand if compressed again.  Try turning drive internal compression off:

It's easy to prevent this from costing too much: Simply prepend a
block of data with a "1" compressed or "0" uncompressed bit. 

Max expansion is then 1 bit per block. (At a cost of one extra bit per
block).

This technique was maybe unacceptable in the old days when you
couldn't afford to buffe a WHOLE block in RAM while you were
compressing to see if it would expand...... 

Nowadays you can easily buffer the data, and still get acceptable
speed, at an acceptable cost in the form of a little higher RAM usage. 

			Roger. 

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots. 
* There are also old, bald pilots. 

  reply	other threads:[~2002-08-01 15:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-30 20:20 st.c block limits ael
2002-08-01  4:45 ` Kai Makisara
2002-08-01 11:46   ` ael
2002-08-01 13:14     ` Tony Battersby
2002-08-01 15:49       ` Rogier Wolff [this message]
2002-08-01 22:51       ` ael
2002-08-01 11:57   ` ael
  -- strict thread matches above, loose matches on Subject: below --
2002-08-01 16:06 Bryan Henderson
2002-08-01 16:53 Bryan Henderson

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=200208011549.RAA05274@cave.bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=law_ence.dev@ntlworld.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tonyb@cybernetics.com \
    /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