> > And that alternative sucks. Think scalability.
> > > 2) Implement a filesystem with realtime response
> > And your shared fs alternative sucks. Think abysmal disk throughput for
> > the rest of the system. Think starvation. Think all the reasons we've been
> > trying to clean up the elevator code times ten. And that's just for the
> > device queue, never mind the deadlock avoidance problems. See "priority
> > inversion".
> What kind of argument is that? It sounds like: because our current block
> interface sucks, all block interfaces suck, and always will. On the
> contrary, I believe our current interface sucks precisely because it is
> not built according to sound principles of realtime design.
No, the above is a theoretical argument about how optimizing disk access
and locking works that's in no way specific to Linux. Remember, hard RT is
trades throughput for latency guarantees. Worst case for this is devices
queues for disks. Go through the thought experiment of what happens when
an RT task and a !RT task interleave disk access. Worse, what happens when
they're creating files (and all the locking that entails) in the same
-- "Love the dolphins," she advised him. "Write by W.A.S.T.E.."
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/