On Thu, 2007-08-09 at 14:49 -0600, Brian Barrett wrote:
> Hi all -
> There was significant discussion this week at the collectives meeting
> about improving the selection logic for collective components. While
> we'd like the automated collectives selection logic laid out in the
> Collv2 document, it was decided that as a first step, we would allow
> more than one + basic compnents to be used for a given communicator.
> This mandated the change of a couple of things in the collectives
> interface, namely how collectives module data is found (passed into a
> function, rather tha a static pointer on the component) and a bit of
> the initialization sequence.
> The revised interface and the rest of the code is available in an svn
> temp branch:
> Thus far, most of the components in common use have been updated.
> The notable exception is the tuned collectives routine, which Ollie
> is updating in the near future.
> If you have any comments on the changes, please let me know. If not,
> the changes will move to the trunk once Ollie is completed with
> updating the tuned component.