Crud, ok. Keep us posted.
On Mar 18, 2008, at 4:16 PM, Josh Hursey wrote:
> I'm testing with checkpoint/restart and the new libevent seems to be
> messing up the checkpoints generated by BLCR. I'll be taking a look
> at it over the next couple of days, but just thought I'd let people
> know. Unfortunately I don't have any more details at the moment.
> -- Josh
> On Mar 17, 2008, at 2:50 PM, Jeff Squyres wrote:
>> WHAT: Bring new version of libevent to the trunk.
>> WHY: Newer version, slightly better performance (lower overheads /
>> lighter weight), properly integrate the use of epoll and other
>> scalable fd monitoring mechanisms.
>> WHERE: 98% of the changes are in opal/event; there's a few changes to
>> configury and one change to the orted.
>> TIMEOUT: COB, Friday, 21 March 2008
>> George/UTK has done the bulk of the work to integrate a new version
>> libevent on the following tmp branch:
>> ** WE WOULD VERY MUCH APPRECIATE IF PEOPLE COULD MTT TEST THIS
>> Cisco ran MTT on this branch on Friday and everything checked out
>> (i.e., no more failures than on the trunk). We just made a few more
>> minor changes today and I'm running MTT again now, but I'm not
>> expecting any new failures (MTT will take several hours). We would
>> like to bring the new libevent in over this upcoming weekend, but
>> would very much appreciate if others could test on their platforms
>> (Cisco tests mainly 64 bit RHEL4U4). This new libevent *should* be a
>> fairly side-effect free change, but it is possible that since we're
>> now using epoll and other scalable fd monitoring tools, we'll run
>> some unanticipated issues on some platforms.
>> Here's a consolidated diff if you want to see the changes:
>> Jeff Squyres
>> Cisco Systems
>> devel mailing list
> devel mailing list