[padb] Réf. : Re: Réf. : Bull changes ( with LSF -mpich2wrapper patch )

[thipadin.seng-long at bull.net]

On Wed, 2010-01-06 at 19:53 +0100,  Ashley Pittman <ashley at pittman.co.uk> wrote:

> On Wed, 2010-01-06 at 16:44 +0100, thipadin.seng-long at bull.net wrote:

>> Yes, I have two on the queue, this one support lsf-mpich2 wrapper. 

>> I have another one in the queue that supports lsf with
>> openmpi-wrapper 
>> If you can deal with both tell me I'll send the patch. 

>Can you send both patches separately to the developers list and I'll
>look at them when I'm home next week.  If you can send the as diffs
>against the svn trunk it's easiest for me, i.e. make the changes and
>then run 'svn diff' and attach the output to a email.  I tend to have
>three or four copies checked out with different un-committed work in
>each.

I get back to you after a short break, as I've been doing some validation 
on a openmpi spawn functionality.
Now I've finished what you've asked me above,  I am just sending both 
patches.
One for lsf-mpich2 wrapper, and the other one with lsf-openmpi wrapper. I 
did it against r386 version.
Both are alike and have many common sub routines. As the patches are 
seperated some routines
are in both patches. I prefer you integrate once as you can factorize.
If you need some 'ps' or 'bjobs' command layouts to understand the coding, 
please ask, I'll send you.



Regards.
Thipadin.




Ashley Pittman <ashley at pittman.co.uk>
01/06/2010 07:53 PM

 
        Pour :  thipadin.seng-long at bull.net
        cc :    florence.vallee at bull.net, Sylvain Jeaugey <sylvain.jeaugey at bull.net>, 
Andry.Razafinjatovo at bull.net
        Objet : Re: Réf. : Bull changes ( with LSF-mpich2 wrapper patch )

On Wed, 2010-01-06 at 16:44 +0100, thipadin.seng-long at bull.net wrote:

> Yes, I have two on the queue, this one support lsf-mpich2 wrapper. 

> I have another one in the queue that supports lsf with
> openmpi-wrapper 
> If you can deal with both tell me I'll send the patch. 

Can you send both patches separately to the developers list and I'll
look at them when I'm home next week.  If you can send the as diffs
against the svn trunk it's easiest for me, i.e. make the changes and
then run 'svn diff' and attach the output to a email.  I tend to have
three or four copies checked out with different un-committed work in
each.

> I would like to include these 2 patches in your next major release, 
> so we can use your version in our official delivery and 
> forget what I've done in version 263 in the early release. 

That sounds ideal, I'm mostly happy with the code now and would like to
make a release as a lot has changed since the last one but lets finish
syncing first.

> > Finally, if you've got access to a 2,000 process job would you mind
> > running some elementary benchmarks for me and sending me the
> results,
> > I've not got access to that scale myself and most of the people I
> deal
> > with are shy about giving out results. 
> 
> Our customer have this, we don't have access to their cluster. 
> By march 2010 we could get access to a cluster with more than 1000
> cores. 
> So when we have this cluster we will test and send you results. 

That would be great.

Ashley,

-- 

Ashley Pittman, Bath, UK.

Padb - A parallel job inspection tool for cluster computing
http://padb.pittman.org.uk



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pittman.org.uk/pipermail/padb-devel_pittman.org.uk/attachments/20100121/79dd54cd/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lsf-mpich2.patch
Type: application/octet-stream
Size: 8834 bytes
Desc: not available
URL: <http://pittman.org.uk/pipermail/padb-devel_pittman.org.uk/attachments/20100121/79dd54cd/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lsf-openmpi.patch
Type: application/octet-stream
Size: 11683 bytes
Desc: not available
URL: <http://pittman.org.uk/pipermail/padb-devel_pittman.org.uk/attachments/20100121/79dd54cd/attachment-0001.obj>