@sg2

Quote:

Indeed, its amazing to see such a close match between the drive specs and the results you got (58 MB/s). This drive is obviously in the 'very few' fast drives category that I mentioned in my post.

and quiet, too. However, my drive is almost new and is spritely enough. Noone in their right mind could justify replacing it. Not in any way.

58MB/s MMMmmmmm.

Regards
Roy Leith

@sg2

Quote:

My scispseed port does not force 32 byte buffer alignment, its just a recompile of Michael Sinz's orginal code. This is why I pointed you to Daniel's more recent diskspeed archive, because he once told me he added proper alignment to my original port. As there is no scsispeed binary in his archive, I'll see to do that myself.

As many have probably seen by now, I've uploaded an updated archive to OS4 Depot.

_________________
This posting, in it's entirety, is the opinion and/or statement of the author and does not reflect the views and/or position of this site.

@DWolfman

Hi Daniel,

At least, I noticed :)

I have tried your make of scsispeed yesterday night, it yelded 35 MB/s, but with a somewhat high CPU usage so I cant say if the buffers were properly aligned or not. Is there a command line switch to enforce 32 byte alignment ?

Also, it crashed with a guru 8000 0005 on exit.

I have not taken time to look into your patches to the source yet.

Regards,
--
Stéphane

@sg2

It enforces 32-byte alignment by default, unless you give it the BYTE or WORD options. That shifts it off the 32-byte alignment by one or two bytes, according to which you choose.

I do need to go back and check that code over I think, and would appreciate your input on it if you get a chance. What I put in there was a somewhat "quick-n-dirty" change to how the memory block is allocated for the buffer, with an extra pointer that is placed near the beginning of the memory block so that it is aligned according to the options (32-byte, then WORD or BYTE alignment shifted from there). I'm not surprised that there could be something in there that caused a guru, but I can honestly say I didn't have that happen regularly on my machine when I tried it out.

I did see it once, but rebooted and tried it again multiple times without any problems. Not sure what caused it and at the time I couldn't find anything in my code that I could place the fault with, so...

Anyway, I also need to add an option for the 32-byte alignment.

_________________
This posting, in it's entirety, is the opinion and/or statement of the author and does not reflect the views and/or position of this site.