1
1

4 Коммитов

Автор SHA1 Сообщение Дата
George Bosilca
9d840343cf Allow just one PTL per process.
This commit was SVN r5772.
2005-05-19 18:17:21 +00:00
George Bosilca
b429c73240 Now we have a way to specify if we want the PML to take care of one or two PTLs by peer. If only
one is selected it will be used for all purposes: small messages and long messages (even if the
long message is still split in several fragments). For the case where 2 PTLs per peer exists,
the first one is for latency (small messages and rendez-vous requests) when the second one
will be used for bandwitdh.

This commit was SVN r5600.
2005-05-05 04:35:18 +00:00
George Bosilca
cb509df2ee More fixes. Remove useless files. Decrease the memory footprint for this PML.
This commit was SVN r5598.
2005-05-05 04:17:52 +00:00
George Bosilca
536a5c5d09 The UNIQ PML is here. It does compile with few warnings, and it still have few bugs. It's here just as a checkpoint.
The idea behind this PML is to minimiza the overhead of managing multiple PTL. For each node, UNIQ keep two PTL's
one for latency and one for bandwidth. One the next version I want to add a configure parameter to allow the user
to select how many PTL's he want: one or two.

This commit was SVN r5593.
2005-05-04 17:08:08 +00:00