George Bosilca 6310ce955c The first patch related to the Active Message stuff. So far, here is what we have: ... - the registration array is now global instead of one by BTL. - each framework have to declare the entries in the registration array reserved. Then it have to define the internal way of sharing (or not) these entries between all components. As an example, the PML will not share as there is only one active PML at any moment, while the BTLs will have to. The tag is 8 bits long, the first 3 are reserved for the framework while the remaining 5 are use internally by each framework. - The registration function is optional. If a BTL do not provide such function, nothing happens. However, in the case where such function is provided in the BTL structure, it will be called by the BML, when a tag is registered. Now, it's time for the second step... Converting OB1 from a switch based PML to an active message one. This commit was SVN r17140.		2008-01-15 05:32:53 +00:00
..
allocator	Per long threads on the mailing list and much confusion discussion	2007-12-15 13:32:02 +00:00
bml	The first patch related to the Active Message stuff. So far, here is what we have:	2008-01-15 05:32:53 +00:00
btl	The first patch related to the Active Message stuff. So far, here is what we have:	2008-01-15 05:32:53 +00:00
coll	The PTLs are now long gone !!!	2008-01-10 00:18:45 +00:00
common	Per long threads on the mailing list and much confusion discussion	2007-12-15 13:32:02 +00:00
crcp	Per long threads on the mailing list and much confusion discussion	2007-12-15 13:32:02 +00:00
io	Per long threads on the mailing list and much confusion discussion	2007-12-15 13:32:02 +00:00
mpool	Don't call free(), or library functions that may call free() inside (such as	2008-01-08 08:55:42 +00:00
mtl	added optional rendezvous protocol for long messages	2008-01-11 22:12:45 +00:00
osc	Per long threads on the mailing list and much confusion discussion	2007-12-15 13:32:02 +00:00
pml	The first patch related to the Active Message stuff. So far, here is what we have:	2008-01-15 05:32:53 +00:00
rcache	Don't call free(), or library functions that may call free() inside (such as	2008-01-08 08:55:42 +00:00
topo	Per long threads on the mailing list and much confusion discussion	2007-12-15 13:32:02 +00:00