-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tony Lee wrote:
| I have to use the non-interrupt mode in sysace. If necessary I will modify the quick patch I posted to use a CONFIG option but several of us are seeing problems with interrupts - I will change it to be the most useful for everyone, I suppose that means making it an option. | Jon, what kind of performance you got from the sysace? Crap. That's a technical term. The chip IMO has some fundamental issues which really need to get resolved in a rev - it takes on the order of several minutes to commit writes with a sync however we rarely have to write to the flash and usually only store small parameter files. | When I copy 18 MB of ace file into sysace with Linux, the | sync command took minutes to complete for me. Where this affects you and I is likely in writes to update the hardware image with a new one that you have sent to the customer as a "firmware upgrade" to be installed. It takes ages for me too - but this is a rare enough thing that we can live with it for the moment. | Sysace ISR should not be the issue, since there is no seeks | and all the IO is dirven from the kernel. The polled approach is worse IMO although I agree that there is very little overhead in the actual ISR. Where the author went wrong (well perhaps not wrong per se but didn't provide enough protection) was in the unlikely case that the hardware is braindead and generates interrupts that you didn't ask it to - the xsysace driver should also catch interrupts when we're QUEUE_EMPTY and should not try to manipulate an empty request queue. Jon. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBZduDeTyyexZHHxERArI0AJ9zd7sRSnO6dZBYw/G3NpuqjNqe7wCgixC0 /eRaHY5fhfUVW7TAFRtCrQM= =3n0G -----END PGP SIGNATURE-----
