I wrote:
> Another idea is to tune the payload of async write requests or
> read responses. [...] I think this could be implemented solely
> in the application layer without intrusion into the transaction
> layer. [...] Implementation questions arise WRT coordination
> between applications
Thus, a central coordination facility besides the transaction
layer would be required. ("Central" in the scope of one node,
that is.)
> both ideas would only allow for a certain degree
> of priorization of exactly two types of transactions: Asynchronous
> block write requests and asynchronous block read responses.
And a 3rd type: Async streaming.
Strictly spoken, other types of async packets would also be affected
but since their packet sizes are small, throughput effects on them
are negligible.
-- Stefan Richter -=====-=-=-- =--= -===- http://arcgraph.de/sr/ ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php _______________________________________________ mailing list Linux1394-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux1394-userReceived on Tue Sep 14 14:49:58 2004
This archive was generated by hypermail 2.1.8 : Mon 02 May 2005 - 09:16:49 CEST