[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4688: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4690: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4691: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4692: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
Parallella Community • View topic - MPI "lite" proof-of-concept

MPI "lite" proof-of-concept

MPI "lite" proof-of-concept

Postby dar » Thu Jan 03, 2013 10:29 am

dar
 
Posts: 90
Joined: Mon Dec 17, 2012 3:26 am

Re: MPI "lite" proof-of-concept

Postby aolofsson » Thu Jan 03, 2013 1:05 pm

WOW, that is incredible! Most people make simple tasks complicated. You make complex tasks look easy.:-)
I talked to a bunch of people about this in the past and received all kinds of reasons why MPI wasn't a good fit for Epiphany. You actually went ahead and implemented a basic MPI programming model in less than a week. Mind boggling! I thank my lucky star that I typed in "GPL OpenCL" in a Google search a year ago to find Brown Deer Technology.:-)

Andreas
User avatar
aolofsson
 
Posts: 1005
Joined: Tue Dec 11, 2012 6:59 pm
Location: Lexington, Massachusetts,USA

Re: MPI "lite" proof-of-concept

Postby ed2k » Sat Jan 05, 2013 5:59 pm

can you give more detail instructions, how to build the brown deer corpthr, where to download the source etc.
ed2k
 
Posts: 113
Joined: Mon Dec 17, 2012 3:27 am

Re: MPI "lite" proof-of-concept

Postby ubii » Sat Jan 05, 2013 6:07 pm

ed2k,

You can download the COPRTHR SDK from the link below and the installation instructions can be found in the COPRTHR Primer.

http://www.browndeertechnology.com/coprthr.htm
User avatar
ubii
 
Posts: 71
Joined: Sun Dec 16, 2012 7:18 pm
Location: US

Re: MPI "lite" proof-of-concept

Postby ed2k » Sun Jan 06, 2013 1:31 am

I visited the website, but unable to download the epiphany package.
I downloaded the git, switch to current branch. the ./configure is really hard to pass on my ubuntu. lots of manual path to satisfy. libelf, libevent, libconfig. wondering have you guys tried it on ubuntu x64 system. Or I need to use a 32bit system.
ed2k
 
Posts: 113
Joined: Mon Dec 17, 2012 3:27 am

Re: MPI "lite" proof-of-concept

Postby ubii » Sun Jan 06, 2013 4:27 am

ed2k,

I was able to get the COPRTHR SDK to install on 64-bit Linux Mint Debian Edition, but it required installing a different version of libelf, as seen below.

In the README.txt, it states the following:

"Please take note that libelf 1.x branch found on most Linux distributions is not a valid substitute for libelf-0.8.13 since they lack the required features and exhibit undocumented broken behavior."

The README.txt file has a to this version of libelf, which you can download and install following the steps listed in the libelf INSTALL.txt file. This will install a different version of libelf, without stepping on your existing version.

After doing this, you should be able to configure, make, and install the COPRTHR SDK, doing the following:

./configure --with-libelf=/usr/local
make
sudo make install
User avatar
ubii
 
Posts: 71
Joined: Sun Dec 16, 2012 7:18 pm
Location: US

Re: MPI "lite" proof-of-concept

Postby ed2k » Sun Jan 06, 2013 5:38 am

got the compilation/installation worked, with lots of manual symbolic link, since the configure always assume the lib is at $THE_PATH/lib and include is at $THE_PATH/include.
now will look into the internal, I am interested to know how corpthr achieve the code deployment without keeping 16 versions of them.
seems libelf is the key.
ed2k
 
Posts: 113
Joined: Mon Dec 17, 2012 3:27 am

Re: MPI "lite" proof-of-concept

Postby dar » Sun Jan 13, 2013 3:21 am

Sorry for slow reply. I need to figure out how to set email notify correctly I guess.

Right now Parallella support is available in a pre-compiled package available for download from www.browndeertechnology.com/coprthr_download.htm (github disabled downloads so we moved the binary downloads here). These builds are being tested on a prototype board and should be considered beta in advance of the next official package release. The source code can be found on github under the current branch. Note that the default on the github project is still 1.4-stable - for Parallella you do not want that branch. Now, unless you have one of the early boards its not clear how easily one can test these builds. We are looking at a way to allow build and test for Parallella without a board to expand accessibility for developers who want to experiment with Parallella programming in advance of a board.

If interested in this MPI "lite" code this is still experimental and has not been merged into current. Sorry.

If you have trouble with building COPRTHR SDK please send questions to support@browndeertechnology.com

The build is tested on a range of platforms and should not require many symbolic links, etc. However, its difficult to catch every platform configuration. We always appreciate feedback to improve the build configuration.

DAR
dar
 
Posts: 90
Joined: Mon Dec 17, 2012 3:26 am

Re: MPI "lite" proof-of-concept

Postby eleitl » Fri Mar 15, 2013 1:33 pm

Do you think it would be feasible to implement a subset of MPI in the spare FPGA space of the new Zynq?
It has enough spare I/O FPGA pins to drive a 6-link 3d grid/torus, and probably can almost
reach 1 GByte/s throughput per link, especially if you can make a cut-through router
so that you don't have to touch internal memory bandwidth for through traffic.
eleitl
 
Posts: 25
Joined: Mon Dec 17, 2012 3:22 am


Return to MPI

Who is online

Users browsing this forum: No registered users and 3 guests

cron