Hi!
Trying to kill the keyboard, [EMAIL PROTECTED] produced:
> Wolfgang Weisselberg wrote:
> > I'd suggest piping the output to 'buffer' and let that program use
> > a couple of megs for buffering[1]. Man buffer should enlighten
> > on it's parameters.
> "man buffer" and "info buffer" say no such thing on my system.
*blink*
Hmm, it should be in your distribution ...
> > [1] Why tune a programm when there is another that was written
> > for such tasks? :-)
> Because my machine does not have it?
That can be mended ...
> How do I tell if I need it? I.e., does
> ftape work any better with larger input blocks?
Well, not with larger input blocks, but with a couple of megs
of data to write held in reserve, there will be less shortages
and thus repositionings just because the HD or cpio has a bit
of latency ...
> I assume once they are larger
> than ftape's internal buffers, it makes no sense to deliver it larger blocks.
Well, no, see above.
> So, how big are those buffers that ftape allocates itself 3 of? Obviously,
> they must be at least 10240 bytes, but are they 30720 bytes or something?
They are 32 Kb long each, aligned at a 32 Kb border. They are
used for DMA. That's in the docs :-)
-Wolfgang
--
PGP 2 welcome: Mail me, subject "send PGP-key".
Unsolicited Bulk E-Mails: *You* pay for ads you never wanted.
How to dominate the Internet/WWW/etc? Destroy the protocols! See:
http://www.opensource.org/halloween.html
