Message Ordering Revisited

Hi,

so far we have been discussing message ordering for the output
ports. But what of the input ports? I have not seen anything
in the spec that tells me what the requirements for message
ordering on input ports are, if any. I think it is fair to
assume that messages to the same ports arrive at the port in
the same order they are sent [1]. But what about messages sent
to different ports? If I send message 1 to port 1 before I send
message 2 to port 2, should message 1 arrive at port 1 before
message 2 arrives at port 2 (the notion of before relates to
uclock cycles)? Or is the implementation free to choose how to
service the queue of pending input messages? Is there an
implementation choice between a single (virtual) queue or
multiple (per-port) queues?

[1] This is a nit, but we should add a sentence to the spec
saying that message ordering within a port (input as well as
output) is strictly preserved.

Per
Received on Fri Mar 12 07:28:55 2004