Thread: [Pypar-developers] Non-blocking communication (reply to justus)
Brought to you by:
uniomni
From: Ole N. <ole...@gm...> - 2008-04-13 05:40:38
|
Oh by the way - the four calls (mpi_isend, mpi_irecv, mpi_wait and mpi_test) you need for non-blocking communication are listed here: http://www.amath.washington.edu/~beowulf/mpi/noblock.html Cheers and good lock On Fri, Apr 11, 2008 at 10:13 AM, Justus Schwabedal <jus...@gm...> wrote: > Hi there. > In my programs a pypar.receive statement is cpu blocking. Is there a > way to not make it block my cpu and just wait until a massage comes in > or is it inherent to mpi? > Yours, Justus > > > On Apr 7, 2008, at 8:23 PM, Ole Nielsen wrote: > > > Ah, I see. > > Your idea is great. The only question is what system to base it on. > > > > Let me know how it goes. > > > > Cheers > > Ole > > > > On Mon, Mar 31, 2008 at 2:25 AM, Justus Schwabedal > > <jus...@gm...> wrote: > >> > >> For what I know you can just help seti by letting them use your > >> computer. > >> But you cannot commit jobs yourself, which is what I was thinking of. > >> > >> > >> > >> > >> On Mar 30, 2008, at 4:39 AM, Ole Nielsen wrote: > >> Hi again Justus > >> > >> I think what you are saying is possible, although I suspect other > >> frameworks > >> migh be better suited for loosely parallel jobs such as SETI@home > >> type > >> frameworks. MPI (and pypar) is specifically geared towards tightly > >> coupled > >> parallel jobs on dedicated clusters. > >> I guess, I am suggesting that you scope the options before settling > >> on > >> pypar. > >> If you go ahead, though, I'll be very interested in following the > >> progress > >> and commenting on designs. > >> > >> Best regards > >> Ole > >> > >> > >> On Fri, Mar 21, 2008 at 1:33 PM, Justus Schwabedal > >> <jus...@gm...> wrote: > >>> > >>> > >>> Good Morning Ole! > >>> I'd be glad to contribute a little although I'm more on the novice > >>> then on > >> the expert side concerning python. To mpi I'm pretty new, but I > >> started to > >> actively work with it recently and I'm farely interested. > >>> You can probably guess the potentials lying in code distribution. > >>> Do you > >> think something like a community parallelization would be possible > >> with > >> python? I'm thinking of something similar to the seti project, but > >> such that > >> everybody can commit jobs and they are distributed intelligentely. > >> What are > >> your thoughts? I'm not quite sure about the technical problems > >> occuring. > >> Afterall it would be absolutely conformal with gnu/linux ideas. One > >> would > >> have to control cpu and memory usage of the "external processes" > >> and the > >> rights they are given on the machine. Well, I guess that's beyond > >> the scope > >> of pypar but also beyond the possible work one could get done in a > >> year or > >> so. > >>> Yours, Justus > >>> > >>> > >>> > >>> > >>> On Mar 20, 2008, at 2:10 PM, Ole Nielsen wrote: > >>> > >>> Hi Justus > >>> > >>> Thank you very much for your mail and your interest in pypar. > >>> Pypar has steadily grown and served us and several others over the > >>> past > >> 6-7 years. > >>> Many people have made contributions over the years and the whole > >>> idea is > >> that pypar should be maintained by a community. > >>> > >>> I think your ideas are great and it wouldn't hurt to throw them > >>> out there > >> for some feedback. If you are keen, I could make an account for you > >> in the > >> subversion repository where pypar lives and your pypar-tools could > >> evolve > >> from there. That'd be great actually. > >>> > >>> As for the adhoc implementation, that'll be fine initially with the > >> understanding that we'd like to see the code base grow into robust, > >> general > >> and flexible tools in the future. > >>> One thing that I have found crucial is the use of a good unit test > >>> suite > >> from the word go as well as version control. I can assist with > >> either. > >>> > >>> The idea of distributing the code as (executable I assume) strings > >>> is > >> definitely novel and interesting. I assume this would be useful for > >> distributed systems that don't have a common NFS mounted filesystem > >> where > >> source code is accessible by all computer nodes. Is that correct? > >>> > >>> Distributing code objecs could be done, but the underlying > >>> implementation > >> would serialise the objects as strings using the underlying MPI > >> calls. > >> Distributing strings is straight forward and probably more efficient. > >>> > >>> I am not aware of anyone else doing this, but it'd be worth a > >>> quick search > >> or post to find out. > >>> > >>> Looking forward to hear more > >>> > >>> Cheers > >>> Ole Nielsen > >>> Canberra, Australia > >>> > >>> > >>> > >>> On Mon, Mar 17, 2008 at 1:28 AM, Justus Schwabedal > >> <jus...@gm...> wrote: > >>> > >>>> Cheers, > >>>> I found out about pypar a couple of weeks ago. I instantly > >>>> started to > >>>> develop a distributed system which distributes source code in the > >>>> form > >>>> of strings. I would like to contribute this into the project by > >>>> maybe > >>>> opening something like pypar-tools. My implementation is kindof > >>>> adhoc > >>>> and I would like to ask if I can get some tips concerning this > >>>> issue. > >>>> Can I distribute code objects instead of strings? Would that be > >>>> more > >>>> efficient? Questions like that are of my concern. Is somebody doing > >>>> something similar? > >>>> Yours, Justus > >>>> > >>>> > >> ------------------------------------------------------------------------- > >>>> This SF.net email is sponsored by: Microsoft > >>>> Defy all challenges. Microsoft(R) Visual Studio 2008. > >>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >>>> _______________________________________________ > >>>> Pypar-developers mailing list > >>>> Pyp...@li... > >>>> https://lists.sourceforge.net/lists/listinfo/pypar-developers > >>>> > >>> > >>> > >>> > >> > >> > >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > Pypar-developers mailing list > Pyp...@li... > https://lists.sourceforge.net/lists/listinfo/pypar-developers > |