Why not? [market research, Linux style]
> pthreads (perhaps not, if you use an event-driven model)
Working.
> disk i/o
What do you want here? The interesting problem is reading from a disk at a
fixed rate, e.g. for display of video or for sound, but this seems
like a buffering problem more than anything else. Writing data is only
a buffering problem. You are almost always better using a smart very
much non-rt file/ i/o system that does reordering, block aggregation,
extents, .... than going to raw hardware.
In RTL we do:
RT task passes request to Linux process: either waits or does not
Linux process does i/o
done
I can trivially implement an "I/O daemon" that will make this transparent, if there is a need.
> possibly shared memory stuff
On the way. Next week probably.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/