In article <1939f831-6a37-476d-8e0d-dbc04c3d4252@27 g2000hsf.google groups.com>,
jurij <jurij.ivastsuk @waxar.euwrote:
....all of which puts you well outside the C language, and therefore
beyond the scope of comp.lang.c.
But if you think carefully about what you have there, it does contain
the essential clue to the answer to your question:
The people in comp.programmin g.threads may be able to give you the
hints you need if you can't work it out yourself.
dave
--
Dave Vandervies dj3vande at eskimo dot com
You know you're studying liberal arts when you see one guy tossing write
rings and his buddy catching them on an epee. Good for hand-eye
co-ordination, that. --Anthony de Boer in the scary devil monastery
jurij <jurij.ivastsuk @waxar.euwrote:
>At first we should mention that we have a one-processor, linux-machine
>(Kernel 2.6.23) and developing an I/O application using g++.
>(Kernel 2.6.23) and developing an I/O application using g++.
beyond the scope of comp.lang.c.
But if you think carefully about what you have there, it does contain
the essential clue to the answer to your question:
>Why our multithreading schema described above cannot give us
>enhancement in speed?
>enhancement in speed?
hints you need if you can't work it out yourself.
dave
--
Dave Vandervies dj3vande at eskimo dot com
You know you're studying liberal arts when you see one guy tossing write
rings and his buddy catching them on an epee. Good for hand-eye
co-ordination, that. --Anthony de Boer in the scary devil monastery