Sending this to devel because we lack a current address for Alex Margolin - can
someone please review the Mosix support requested to transfer to v1.7 in CMR
#3411? We need (a) to know the status of that code, (b) is it already in the
trunk, and (c) a patch.
If it isn't in the trunk, then let's
Ok; thanks.
It looks like this should go to v1.6, too -- right (Nathan/George/Brian)?
On Apr 24, 2013, at 9:31 PM, Ralph Castain wrote:
> This was already resolved - Nathan applied it, and it has been moved into v1.7
>
> On Apr 24, 2013, at 5:53 PM, "Jeff Squyres (jsquyres)"
> wrote:
>
>>
This was already resolved - Nathan applied it, and it has been moved into v1.7
On Apr 24, 2013, at 5:53 PM, "Jeff Squyres (jsquyres)"
wrote:
> George / Brian / Nathan --
>
> Can you guys comment on this patch?
>
>
> On Apr 4, 2013, at 4:40 PM, Martin SCHREIBER
> wrote:
>
>> Dear developer
George / Brian / Nathan --
Can you guys comment on this patch?
On Apr 4, 2013, at 4:40 PM, Martin SCHREIBER wrote:
> Dear developers,
>
> it seems that for messages of size 0 no convertor is created due to
> optimizations issues.
> However, this is not considered in MCA_PML_OB1_SEND_REQUEST_R
I could probably do Monday afternoon and Tuesday morning? The problem with
Friday afternoon is that it means I can't grab the Friday afternoon flights
home and have to stay until Saturday. Monday afternoon / Tuesday morning would
mean no weekend travel.
Brian
--
Brian W. Barrett
Scalable
Jeff confirmed off-list that the June Forum meets in San Jose - so I'm
available for it.
On Apr 24, 2013, at 6:54 AM, Jeff Squyres (jsquyres) wrote:
> The idea came up on the call yesterday that it might well be worthwhile to
> have another development meeting mid/late summer. Of particular
The idea came up on the call yesterday that it might well be worthwhile to have
another development meeting mid/late summer. Of particular interest is design
discussions about asynchronous progress.
The next MPI Forum meeting runs 1pm June 4 (Tue) through noon June 7 (Fri).
Assuming that seve
Thanks for identifying that it was the same bug that George recently fixed.
I literally committed that fix to the v1.6 tree earlier this morning. It will
therefore be in tonight's 1.6.x nightly tarball, and will be included in 1.6.5.
On Apr 23, 2013, at 9:37 PM, Eric Chamberland
wrote:
> Hi
