Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.programming > #1287

Re: async I/O

Cross-posted to 2 groups.

Show all headers | View raw

"Jens Thoms Toerring" <jt@toerring.de> wrote in message 
news:9p8o2iFub5U1@mid.uni-berlin.de...
> I'm a bit puzzled what you mean by "asynchrounous messaging" and
> "control messages" - my applogies if I miss the core of your pro-
> blem completely. From what else you write I get the impression
> that you have a number of pipes
>

By asynchronous messages I mean that they were sent out via async 
communication methods. 'Control messages' are just the protocol specific 
commands transferred in such async messages.

Thank you for clarifying me the underlying mechanisms. So it is very likely 
to have a race condition with multiple pipes, as you described:

A -> B
A -> C
B -> C
C -> A

[snip]
> There is nothing that would ensure that process B will be run
> before process C just because your process A first wrote to a
> pipe to B and only then to a pipe to C. The operating system
> schedules processes for running by a lot of different criteria
> and you can never, ever rely on any certain order (well, un-
> less you have read und understood the kernel sources in every
> relevant detail and you are prepared to adjust your program
> for every release of the kernel in existence;-)

Mark 

Back to comp.programming | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

async I/O "Mark" <mark_cruzNOTFORSPAM@hotmail.com> - 2012-02-05 17:52 -0500
  Re: async I/O jt@toerring.de (Jens Thoms Toerring) - 2012-02-06 01:18 +0000
    Re: async I/O "Mark" <mark_cruzNOTFORSPAM@hotmail.com> - 2012-02-05 22:43 -0500
  Re: async I/O Eric Sosman <esosman@ieee-dot-org.invalid> - 2012-02-06 00:38 -0500
  Re: async I/O scott@slp53.sl.home (Scott Lurndal) - 2012-02-06 16:11 +0000

csiph-web