Re: 2048 byte/sector problems with kernel 2.4

Harvey Fishman (fishman@panix.com)
Tue, 3 Apr 2001 18:48:06 -0400 (EDT)


On Tue, 3 Apr 2001, Alan Cox wrote:

> > I also tried it with 2.2.18 there it works but it seems to be utterly
> > slow. I'm using kernel 2.4.2(XFS version to be precise).
>
> M/O disks are slow. At a minimum make sure you are using a physical block size
> of 2048 bytes when using 2048 byte media and plenty of memory to cache stuff
> when reading. Seek times on M/O media are pretty poor

Another thing making for the snailicity of MO drives is that writing is a
two pass operation. It is very like core memory; first you write the spot
to a known state, and then you write the data. So you have an average
latency of 25 mS. for write operations and 8.33 mS. for read operations.
There WERE direct overwrite media for a while that would, in theory, be
able to write the data directly, but a combination of high cost, limited
sources, and strong questions about the permanence of the recorded data
severely limited the demand for these and I think that they have been
withdrawn.

Harvey

----------------------------------------------------------------------------
Harvey Fishman |
fishman@panix.com | A little heresy is good for the soul.
718-258-7276 |

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/