On Jul 22, 2009, at 1:54 PM, Bert Wesarg wrote:
> On Wed, Jul 22, 2009 at 19:24, Jeff Squyres<jsquyres_at_[hidden]> wrote:
> > Bert -- is this functionality something we'd want to incorporate
> into PLPA?
> What functionality? The complete libcpuset or just the 'get me the
> cpuset mask of this task'? I don't think its good if we duplicate the
> whole functionality of the libcpuset and taking libcpuset as a
> dependency of PLPA sounds too heavy. Actually I really don't know yet.
>
Moving this particular chunk to the PLPA list...
Ditto (meaning: I don't know). Someone asked me a month or two ago if
we should be incorporating some flavor of cpuset support in PLPA and
my reply was about the same: hmm. I don't know.
Unfortunately, I haven't had a chance to think about it since. :-\
I agree that (I don't think that) we wouldn't want to duplicate or
subsume the functionality of libcpuset in PLPA. But is there some
kind of interaction that would make sense that they can work together
-- i.e., PLPA can use libcpuset to provide additional information?
I'm not opposed to making libcpuset a *conditional* dependency to
PLPA. If configure finds it, PLPA will build support for it and try
to use it at run-time. If not, the corresponding PLPA functions will
return -ENOSYS (or whatever).
--
Jeff Squyres
jsquyres_at_[hidden]
|
![[Flag]](../../../../../community/mirrors/flag-us.gif){kind=small}