bbenton -> bbenton
On Wed, Sep 10, 2014 at 5:46 AM, Jeff Squyres (jsquyres) wrote:
> As the next step of the planned migration to Github, I need to know:
>
> - Your Github ID (so that you can be added to the new OMPI git repo)
> - Your SVN ID (so that I can map SVN->Github IDs, and therefore map
I am running into similar issues with both Mellanox and IBM HCAs.
On a node installed with RHEL6.2 and MLNX_OFED-1.5.3-3.0.0, there is a
significant hit to locked memory when going with the device's max_cqe.
Here, for comparison's sake is the memory utilization for a simple MPI
process when using
What IP interfaces are configured on the cluster? In particular, are there
IPoIB interfaces that are configured? If you use the dynamic connection
method but restrict either the number or type of IP interfaces to be used
via oob_tcp_if_{include,exclude}, do you still see the problem?
--brad
On
On Tue, Jun 29, 2010 at 10:38 AM, Jeff Squyres wrote:
> Rainer and I are feeling good about v1.5; it is possible we could release
> within a week.
>
> Can we get a thumbs up / down from each organization about where you think
> we are with v1.5? Cisco and HLRS obviously give a thumbs up.
>
Our
On Wed, Nov 11, 2009 at 10:29 AM, Terry Dontje wrote:
> Jeff Squyres wrote:
>
>> On Nov 11, 2009, at 8:13 AM, Terry Dontje wrote:
>>
>> Sun's IB group has asked me to forward the following email to see if
>>> anyone has any comments on this email.
>>>
>>>
>> Tastes great / less filling. :-)
>>
>
>
> On Jun 16, 2009, at 10:37 PM, Brad Benton wrote:
>
> All:
>>
>> We are close to releasing 1.3.3. This is the current plan:
>> - Evening of 6/16: collect MTT runs on the current branch w/the current
>> 1.3.3 features & fixes
>> - If all go
All:
We are close to releasing 1.3.3. This is the current plan:
- Evening of 6/16: collect MTT runs on the current branch w/the current
1.3.3 features & fixes
- If all goes well with the overnight MTT runs, roll a release candidate
on 6/17
- Put 1.3.3rc1 through its paces over the next coupl
In reference to this critical bug, there are implications for the current
1.3.x release schedule that are alluded to in Jeff's message. In
particular, there are two time-critical issues at play:
1) getting a fix for #1853 in time for inclusion for OFED-1.4.1 2)
getting in Sun's changes/CMRs in
Things look good from the IBM side as well. So, RM-approved for release.
--brad
ompi 1.3 co-release manager
On Thu, Mar 19, 2009 at 7:31 AM, Jeff Squyres wrote:
> Looks good to cisco. Ship it.
>
> I'm still seeing a very low incidence of the sm segv during startup (.01%
> -- 23 tests out of
Ahh...replied to the MTT segv thread...but will reiterate here: George & I
talked and we are in agreement that we should go ahead and release 1.3.1 as
it currently stands.
Now on to 1.3.2!
--brad
On Thu, Mar 12, 2009 at 7:52 AM, Jeff Squyres wrote:
> So -- RM's -- can we release 1.3.1? The t
I think that this is relatively contained and has not been seen out of MTT
under normal operating conditions. Also, as Jeff has argued, it doesn't
appear to be a regression against 1.3. George & I talked about this and we
are in agreement that we should go ahead and release 1.3.1 as it currently
r20275 looks good. I suggest that we CMR that into 1.3 and get rc6 rolled
and tested. (actually, Jeff just did the CMR...so off to rc6)
--brad
On Wed, Jan 14, 2009 at 1:16 PM, Edgar Gabriel wrote:
> so I am not entirely sure why the bug only happened on trunk, it could in
> theory also appear
So, if it looks okay on 1.3...then there should not be anything holding up
the release, right? Otherwise, George we need to decide on whether or not
this is a blocker, or if we go ahead and release with this as a known issue
and schedule the fix for 1.3.1. My vote is to go ahead and release, but
track for a release on Dec. 16. However, if it is not resolved by the end
of the week, the reality is that this release will then most likely slip to
January.
I will post an update on the progress and revised schedule this Friday.
--brad
Brad Benton
Open MPI v1.3 co-release manager
On Tue, Dec 2
the release candidates as they become available.
Thanks,
--brad
Brad Benton
Open MPI v1.3 co-release manager
Ralph,
I've just tried this out in my environment where I was seeing issues (as
reported in #1661) and it looks good to me. Now I'm not seeing any drops.
Thanks,
--brad
On Thu, Nov 20, 2008 at 2:25 PM, Ralph Castain wrote:
> Hi all
>
> I believe I have fixed the IOF problems reported by Tim M
st what you can commit to testing. This will
help us all
release a better and more stable product.
thanks,
--brad
Brad Benton
v1.3 co-release manager
Greg,
Here is the latest schedule that we have for getting 1.3 out the door:
https://svn.open-mpi.org/trac/ompi/milestone/Open%20MPI%201.3
Basically, this schedule sets Nov. 10 as the release date with a backup date
of Nov. 17.
Here is a bit more detail as to the release to beta and then to releas
On Mon, Jul 28, 2008 at 12:08 PM, Terry Dontje wrote:
> Jeff Squyres wrote:
>
>> On Jul 28, 2008, at 12:03 PM, George Bosilca wrote:
>>
>> Interesting. The self is only used for local communications. I don't
>>> expect that any benchmark execute such communications, but apparently I was
>>> wron
My experience is the same a Lenny's. I've tested on x86_64 and ppc64
systems and tests using --mca btl openib,self hang in all cases.
--brad
2008/7/28 Lenny Verkhovsky
> I failed to run on different nodes or on the same node via self,openib
>
>
>
> On 7/28/08, Ralph Castain wrote:
>>
>> I c
I think this is very reasonable to go ahead and include for 1.3. I find
that preferable to a 1.3-specific "wonky" workaround. Plus, this sounds
like something that is very good to have in general.
--brad
On Wed, Jul 9, 2008 at 8:49 PM, Jeff Squyres wrote:
> v1.3 RMs: Due to some recent work,
All:
The trunk is now ready to be branched for the 1.3 release. Jeff has
volunteered to do the branch in his copious spare time (thanks Jeff!). So,
I expect that to happen either this evening or sometime tomorrow.
There are numerous tickets to resolve to get 1.3 ready for release. So, for
the
I think this is a good idea, and for the reasons you outline in your
Rationale. This definitely bites people from time to time at Big Blue as
well, and a gentle warning will certainly help.
--brad
On Mon, Jun 23, 2008 at 8:42 AM, Jeff Squyres wrote:
> Those who care about the openib BTL:
>
>
Brian,
This is working smoothly now: both the configuration/build and execution.
So,
from my standpoint, it looks good for inclusion into the trunk.
--brad
On Wed, Jun 11, 2008 at 4:50 PM, Brian W. Barrett
wrote:
> Brad unfortunately figured out I had done something to annoy the gods of
> m
np...i'll give it another try (and will correspondingly endeavor to mollify
the mercurial gods
as best i can).
thx,
--brad
On Wed, Jun 11, 2008 at 4:50 PM, Brian W. Barrett
wrote:
> Brad unfortunately figured out I had done something to annoy the gods of
> mercurial and the repository below di
George has an objection, I'm fine with
that.
--Brad
>
> Rich
>
>
>
> On 5/20/08 5:53 PM, "Brad Benton" wrote:
>
> All:
>
> In order to better track changes on the trunk until we branch for 1.3, we
> (the release managers) would like to ask tha
All:
In order to better track changes on the trunk until we branch for 1.3, we
(the release managers) would like to ask that all trunk checkins have
corresponding tickets associated with them. This will help us to keep
better track of the state of the trunk prior to branching. Note, this is
just
Yes...bug fixes are definitely allowed. We won't go to controlled commits
until after branching.
--brad
On Wed, May 14, 2008 at 8:39 AM, Terry Dontje wrote:
> I am right to assume that bug fixes are allowed.
>
> --td
>
> Brad Benton wrote:
> > All:
> >
>
(cutoff date for them is May 20)
- Final parts of 1.3 Thread Multiple Support
- Send & Receive changes for improved latency
(#1250<https://svn.open-mpi.org/trac/ompi/ticket/1250>
)
- XML component for orte_output() and friends
Thanks,
--Brad
Brad Benton
Open M
All:
We are now at the point where Ralph is ready to merge the changes he has
been making to ORTE into the trunk. This is a major item for the
1.3release and its inclusion into the trunk will enable it to be
tested and
stabilized on a wider variety of environments. To make this merge as smooth
a
or my fellow
1.3co-release manager George Bosilca (
bosi...@eecs.utk.edu) know of any issues, errors, suggestions, omissions,
heartburn, etc.
Thanks,
--Brad
Brad Benton
IBM
31 matches
Mail list logo
