linuxaudio.org

--nextPart1635534.bm64DpStDS

Content-Type: text/plain;

  charset="iso-8859-1"

Content-Transfer-Encoding: quoted-printable

Content-Disposition: inline
On Wednesday 09 September 2009 14:25:17 James Cameron wrote:

quoted text
> On Wed, Sep 09, 2009 at 06:05:23PM +0800, Ray Rashif wrote:

> > No, you're right, hdparm is raw r/w and sees no FS. Slipped my mind for=

 a

quoted text
> > moment.

> Well ... you *might* create a big file on the filesystem, then use

> losetup to bind it to a block device, and *then* use hdparm on that

> loopback device.  ;-)

If file systems have problems with continuous reads from a continuous file.

Otherwise I really doubt that you will see something file-system specific.
BTW: Doing a real benchmark still requires one run with hdparm to get the=20

maximum values for the transfer rates...
> Opinion ... I've never found any use for filesystem performance

quoted text
> measurement in audio applications ... it has never been the critical

> path for me.  As soon as the total data flow approaches the limit

> imposed by the filesystem, then anything can cause a pause ... even a

> disk drive thermal recalibration or a response to excessive vibration.

> Such things cause a momentary delay, and if I'm trying to use the disk

> the filesystem I'm using won't matter at all.

I think for plain recording it shouldn't make a difference. When playback=20

occurs, there are multiple files involved and it could be the seeks also de=

pend=20

on how the file systems lays out the files on disk. So that might have an=20

influence. If this information isn't cached in ram.
Otherwise its just a matter of taste and bad experience. For example there =

are=20

three types of people regarding reiserfs: Those that haven't used it yet,=20

those that have used it and love it and finally those that had used it and =

lost=20

data because of it...
Arnold
--nextPart1635534.bm64DpStDS

Content-Type: application/pgp-signature; name=signature.asc

Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----

Version: GnuPG v1.4.9 (GNU/Linux)
iEYEABECAAYFAkqnqOsACgkQuYLL1cDjHx1KSgCeJlQB4jytTmTwf8/uDObHRc08

qsMAnA02MDowDO8c3Xpd7PE+3FxK5udH

=aKcN

-----END PGP SIGNATURE-----
--nextPart1635534.bm64DpStDS--