<br><font size=2 face="sans-serif">Ok .. could we add the IBMers to both
the -dev and -bg lists? </font>
<br>
<br><font size=2 face="sans-serif">Thanks!</font>
<br>
<br><font size=2 face="sans-serif">Michael Blocksome<br>
Blue Gene Messaging Team Lead<br>
Advanced Systems SW Development<br>
blocksom@us.ibm.com<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Rob Ross <rross@mcs.anl.gov></b>
</font>
<br><font size=1 face="sans-serif">Sent by: dcmf-bounces@lists.anl-external.org</font>
<p><font size=1 face="sans-serif">02/28/2008 01:29 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">"Rajeev Thakur" <thakur@mcs.anl.gov></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">dcmf-bounces@lists.anl-external.org,
dcmf@lists.anl-external.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [dcmf] 32-bit ROMIO: What is the
best solution?</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Let's just use mpich2-bg. -- Rob<br>
<br>
On Feb 28, 2008, at 1:26 PM, Rajeev Thakur wrote:<br>
<br>
> Perhaps we could use mpich2-bg for private communication between the
<br>
> IBM<br>
> folks and Argonne MPICH2 developers, and mpich2-dev for stuff meant
<br>
> for<br>
> others. mpich2-dev has many subscribers.<br>
><br>
> Rajeev<br>
><br>
><br>
>> -----Original Message-----<br>
>> From: dcmf-bounces@lists.anl-external.org<br>
>> [mailto:dcmf-bounces@lists.anl-external.org] On Behalf Of Rob
Ross<br>
>> Sent: Thursday, February 28, 2008 12:56 PM<br>
>> To: Pavan Balaji<br>
>> Cc: dcmf@lists.anl-external.org; dcmf-bounces@lists.anl-external.org<br>
>> Subject: Re: [dcmf] 32-bit ROMIO: What is the best solution?<br>
>><br>
>> That's fine with me too. Michael, please provide us a list of<br>
>> interested IBM parties, and we'll get this set up.<br>
>><br>
>> Pavan, can you put RobL, Kevin, Sam, and I on the mpich2-bg list<br>
>> (along with Rajeev and others on the MPICH team as appropriate)?<br>
>><br>
>> Thanks,<br>
>><br>
>> Rob<br>
>><br>
>> On Feb 28, 2008, at 12:42 PM, Pavan Balaji wrote:<br>
>><br>
>>><br>
>>> There's an mpich2-bg list that I just created if you want
to move<br>
>>> there.<br>
>>><br>
>>> -- Pavan<br>
>>><br>
>>> On 02/28/2008 12:39 PM, Rob Ross wrote:<br>
>>>> Rajeev had suggested this too. Let's go with mpich2-dev.
Can you<br>
>>>> give us a list of people that should be added to the list?<br>
>>>> Thanks,<br>
>>>> Rob<br>
>>>> On Feb 28, 2008, at 12:29 PM, Michael Blocksome wrote:<br>
>>>>><br>
>>>>> I agree .. we need to get over the discussion about
the<br>
>> discussion<br>
>>>>> as fast as possible. :)<br>
>>>>><br>
>>>>> The dcmf list has worked well, but I think we started
using it<br>
>>>>> because there were no alternatives to the issue at
hand. Given<br>
>>>>> that the mpich2 and global arrays communities have
different<br>
>>>>> licenses, our long term direction for the dcmf community<br>
>> should be<br>
>>>>> to support the dcmf library and move discussion of
other<br>
>>>>> "external" libraries (like mpich2 and global
arrays) into thier<br>
>>>>> communities.<br>
>>>>><br>
>>>>> I just noticed that there is a mpich2-dev@mcs.anl.gov<br>
>> mailing list<br>
>>>>> already set up. Could we use this list to collaborate
on the<br>
>>>>> mpich2 implementation?<br>
>>>>><br>
>>>>> Michael Blocksome<br>
>>>>> Blue Gene Messaging Team Lead<br>
>>>>> Advanced Systems SW Development<br>
>>>>> blocksom@us.ibm.com<br>
>>>>><br>
>>>>><br>
>>>>> Rob Ross <rross@mcs.anl.gov> wrote on 02/28/2008
12:17:06 PM:<br>
>>>>><br>
>>>>>> Hi,<br>
>>>>>><br>
>>>>>> We've been using the DCMF list for all sorts of
things<br>
>> that aren't<br>
>>>>>> directly related to DCMF without any issues (as
far as<br>
>> I know);<br>
>>>>> it has<br>
>>>>>> become the successful technical communication
path between IBM<br>
>>>>> and ANL<br>
>>>>>> so far.<br>
>>>>>><br>
>>>>>> However, if you'd like to create a separate list
for<br>
>> discussing<br>
>>>>> this,<br>
>>>>>> we can do that. Is that what you would like to
do? If so, can<br>
>>>>> you give<br>
>>>>>> us a list of people on the IBM side that should
be on the new<br>
>>>>> list?<br>
>>>>>> I'd like to be done discussing where we're going
to talk about<br>
>>>>> this<br>
>>>>>> issue ASAP and concentrate on fixing it.<br>
>>>>>><br>
>>>>>> Thanks,<br>
>>>>>><br>
>>>>>> Rob<br>
>>>>>><br>
>>>>>> On Feb 28, 2008, at 11:18 AM, Michael Blocksome
wrote:<br>
>>>>>><br>
>>>>>>><br>
>>>>>>> Unfortunately, this MPI_Aint discussion really
has<br>
>> nothing to do<br>
>>>>>>> with DCMF. The entrire problem and solution
is with MPICH2.<br>
>>>>>>><br>
>>>>>>> Is there another, less broad, mpich mailing
list that<br>
>> we could<br>
>>>>> use?<br>
>>>>>>> Maybe a "mpich-development" or something
like that?<br>
>>>>>>><br>
>>>>>>> Michael Blocksome<br>
>>>>>>> Blue Gene Messaging Team Lead<br>
>>>>>>> Advanced Systems SW Development<br>
>>>>>>> blocksom@us.ibm.com<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> dcmf-bounces@lists.anl-external.org wrote
on 02/28/2008<br>
>>>>> 11:01:09 AM:<br>
>>>>>>><br>
>>>>>>>> I'd say this mailing list is better for
it right now.<br>
>>>>> Posting on the<br>
>>>>>>>> broader mpich-discuss might just distract
us.<br>
>>>>>>>><br>
>>>>>>>> Rajeev<br>
>>>>>>>><br>
>>>>>>>> From: dcmf-bounces@lists.anl-external.org
[mailto:dcmf-<br>
>>>>>>>> bounces@lists.anl-external.org] On Behalf
Of Bob Cernohous<br>
>>>>>>>> Sent: Wednesday, February 27, 2008 4:19
PM<br>
>>>>>>>> To: dcmf@lists.anl-external.org<br>
>>>>>>>> Subject: Re: [dcmf] 32-bit ROMIO: What
is the best solution?<br>
>>>>>>><br>
>>>>>>>><br>
>>>>>>>> bobc@us.ibm.com wrote on 02/08/2008 02:41:40
PM:<br>
>>>>>>>><br>
>>>>>>>>> We all realize there are issues with
MPI_Aint's in 32 bit<br>
>>>>>>> implementations.<br>
>>>>>>>>> Using signed 32 bit addresses along
with 64 bit offsets can<br>
>>>>>>> result in<br>
>>>>>>>>> some pretty broken code. I've
reproduced several<br>
>> problems on<br>
>>>>>>>>> BGL/BGP/linux. The problems
are most obvious with romio<br>
>>>>> files ><br>
>>>>>>> 2G or<br>
>>>>>>>>> virtual addresses > 2G.<br>
>>>>>>>><br>
>>>>>>>> Earlier this month I posted some comments
to this mailing<br>
>>>>> list about<br>
>>>>>>>> 32-bit MPICH/ROMIO/MPI_Aint issues (see
above and the<br>
>>>>> archive).<br>
>>>>>>>><br>
>>>>>>>> We've started to work on the problem.
We're (optionally)<br>
>>>>> making<br>
>>>>>>>> MPI_Aint a 64 bit signed value even when
integers/pointers<br>
>>>>> are 32<br>
>>>>>>> bit<br>
>>>>>>>> values.<br>
>>>>>>>><br>
>>>>>>>> We'd like to start sending fix patches
to the<br>
>> community for<br>
>>>>> comment.<br>
>>>>>>>><br>
>>>>>>>> However, since we are (in parallel) contributing
our BGP<br>
>>>>> code back<br>
>>>>>>>> to MPICH and trying to converge on a common
code base of<br>
>>>>> 1.0.7,<br>
>>>>>>>> and because this problem applies to any
32-bit platform,<br>
>>>>>>>> we thought we should move the discussion
to<br>
>> mpich-discuss to<br>
>>>>> get<br>
>>>>>>>> the larger community's comments.<br>
>>>>>>>><br>
>>>>>>>> It's unlikely, at this point, that our
patches<br>
>> would apply to<br>
>>>>>>> MPICH2,<br>
>>>>>>>> but that is our goal after the 1.0.7/BGP
patch settles.<br>
>>>>> For now,<br>
>>>>>>> we'd<br>
>>>>>>>> be sending these as RFC (request for comment)
patches.<br>
>>>>>>>><br>
>>>>>>>> Please let us know if you agree with discussing<br>
>> this on mpich-<br>
>>>>>>> discuss,<br>
>>>>>>>> or if there is a better place.<br>
>>>>>>>><br>
>>>>>>>> Bob Cernohous: (T/L 553) 507-253-6093<br>
>>>>>>>><br>
>>>>>>>> BobC@us.ibm.com<br>
>>>>>>>> IBM Rochester, Building 030-2(C335), Department
61L<br>
>>>>>>>> 3605 Hwy 52 North, Rochester, MN
55901-7829<br>
>>>>>>>><br>
>>>>>>>>> Chaos reigns within.<br>
>>>>>>>>> Reflect, repent, and reboot.<br>
>>>>>>>>> Order shall<br>
>>>>> return._______________________________________________<br>
>>>>>>>> dcmf mailing list<br>
>>>>>>>> dcmf@lists.anl-external.org<br>
>>>>>>>> http://lists.anl-external.org/cgi-bin/mailman/listinfo/dcmf<br>
>>>>>>>> http://dcmf.anl-external.<br>
>>>>>> org/wiki_______________________________________________<br>
>>>>>>> dcmf mailing list<br>
>>>>>>> dcmf@lists.anl-external.org<br>
>>>>>>> http://lists.anl-external.org/cgi-bin/mailman/listinfo/dcmf<br>
>>>>>>> http://dcmf.anl-external.org/wiki<br>
>>>>>><br>
>>>> _______________________________________________<br>
>>>> dcmf mailing list<br>
>>>> dcmf@lists.anl-external.org<br>
>>>> http://lists.anl-external.org/cgi-bin/mailman/listinfo/dcmf<br>
>>>> http://dcmf.anl-external.org/wiki<br>
>>><br>
>>> -- <br>
>>> Pavan Balaji<br>
>>> http://www.mcs.anl.gov/~balaji<br>
>>><br>
>><br>
>> _______________________________________________<br>
>> dcmf mailing list<br>
>> dcmf@lists.anl-external.org<br>
>> http://lists.anl-external.org/cgi-bin/mailman/listinfo/dcmf<br>
>> http://dcmf.anl-external.org/wiki<br>
>><br>
>><br>
><br>
<br>
_______________________________________________<br>
dcmf mailing list<br>
dcmf@lists.anl-external.org<br>
http://lists.anl-external.org/cgi-bin/mailman/listinfo/dcmf<br>
http://dcmf.anl-external.org/wiki<br>
</font></tt>
<br>