If your running windows (NT or 2k), the bottle neck is the OS. The NT microkernel was designed serialize all IDE device access in the drivers. Therefore, if multiple processes are attempting concurrent IDE subsystem access, each data transfer request will run to completion.
It actually makes no difference if the processes are attempting access to different physical devices, because it is the NT driver layer that enforces this restriction. This is especially bad for an OS that relies on a page/swap file residing on a shared resource.
Only viable solution for concurrent access: use only SCSI devices.
Is anyone realy suprised by this?
In an age where public funding for higher education, in the US, is on the decline, public institutions will do what it takes to remain open.
Yes, I've used MontaVista's real-time distro. but only for soft real-time tasks. It could'nt keep up with transcoding ATM AAL-1 to AAL-1 at OC-48 Line rates. For Hard real-time requirements you just can't beat uC/OS-II.
Slashdot Mirror
If your running windows (NT or 2k), the bottle neck is the OS.
The NT microkernel was designed serialize all IDE device access in the drivers.
Therefore, if multiple processes are attempting concurrent IDE subsystem access, each data transfer request will run to completion.
It actually makes no difference if the processes are attempting access to different physical devices, because it is the NT driver layer that enforces this restriction.
This is especially bad for an OS that relies on a page/swap file residing on a shared resource.
Only viable solution for concurrent access: use only SCSI devices.
Is anyone realy suprised by this?
In an age where public funding for higher education, in the US, is on the decline, public institutions will do what it takes to remain open.
There is, it's from McCabe.
Yes, I've used MontaVista's real-time distro. but only for soft real-time tasks. It could'nt keep up with transcoding ATM AAL-1 to AAL-1 at OC-48 Line rates. For Hard real-time requirements you just can't beat uC/OS-II.