Gaurav Khanna | 20 Jul 19:23 2014

OpenCL Linux port


Hi Folks —

I’m looking for an OpenCL x86_64 Linux port for the RC5 application. I have a whole bunch of AMD Radeon HD 7970s, R9 290x and even a few R9 295x2. 
I see the Windows version, but I need a Linux (Ubuntu) port. Any suggestions?

Thanks much,
Gaurav

-----------------------------------------------

GAURAV KHANNA
UMass Dartmouth, Physics
(508) 910 6605
http://gravity.phy.umassd.edu/

"Black holes are where God divided by zero." - Steven Wright



_______________________________________________
rc5 mailing list
rc5@...
http://lists.distributed.net/mailman/listinfo/rc5
Jeff Leigh | 28 Jun 17:33 2014
Picon

Keyservers having issues?

I've been getting a lot of messages like this the last few hours where the client can't connect:

[Jun 28 12:51:38 UTC] Connect to host us.v29.distributed.net:2064 failed.      
                      ENOSYS: unsupported system call
[Jun 28 13:51:38 UTC] Connect to host us.v29.distributed.net:2064 failed.      
                      ENOSYS: unsupported system call
[Jun 28 14:51:38 UTC] Connect to host us.v29.distributed.net:2064 failed.      
                      ENOSYS: unsupported system call

Anyone know what's going on?
_______________________________________________
rc5 mailing list
rc5@...
http://lists.distributed.net/mailman/listinfo/rc5
NODEraser | 22 Apr 03:38 2014
Picon

Mac OS 9 Client

Would the client for Classic Mac OS still work with the project, or
was there a change somewhere along the way that makes it useless? If
it is still viable, where could I find it? I googled the filename, and
the results all pointed toward the old download url which is no longer
active.

--

-- 
[Greg Bennett]
-Independent Carpenter, Electrician & Lighting Designer
-Purveyor of Classic Apple & Macintosh Gear
http://www.hsiprodsvcs.com/
http://www.macshack.us/
_______________________________________________
rc5 mailing list
rc5@...
http://lists.distributed.net/mailman/listinfo/rc5

Mike Reed | 15 Mar 13:05 2014
Picon

RC5!

Yesterday was Pi day.. in the US.

By cosmic coincidence, we also passed 3.14% complete on RC5-72 :)

Keep on crunching!

Moo!
_______________________________________________
rc5 mailing list
rc5@...
http://lists.distributed.net/mailman/listinfo/rc5

\neena | 7 Mar 07:16 2014
Picon

(no subject)

_______________________________________________
rc5 mailing list
rc5@...
http://lists.distributed.net/mailman/listinfo/rc5
waldo kitty | 19 Feb 21:41 2014
X-Face
Picon

bad link in OGR faq


the link to mark garry's old aol page is broken... it goes to some sort of 
lifestream site that wants you to sign up instead of showing mark's page...

http://faq.distributed.net/cache/266.html

--

-- 
NOTE: No off-list assistance is given without prior approval.
       Please keep mailing list traffic on the list unless
       private contact is specifically requested and granted.
_______________________________________________
rc5 mailing list
rc5@...
http://lists.distributed.net/mailman/listinfo/rc5

Beckert | 19 Feb 21:13 2014
Picon
Picon

OGR-28 started

Hello,

since OGR-27 finished and OGR-28 has started.
What was the best OGR-27 ruler and was a better one found?
What is so far the best known OGR-28 ruler?
What are the best known rulers for rulers with more marks?

Kind regards.
_______________________________________________
rc5 mailing list
rc5@...
http://lists.distributed.net/mailman/listinfo/rc5

Toomas Aas | 18 Feb 20:00 2014
Picon

Personal proxy not honoring buffer size settings

Hello!

I've been running a personal proxy for almost as long as I've been  
involved in distributed.net, which is since 1997. The current version  
that I have is build 347 running on FreeBSD 7.4.

For last several years I've been concentrating mostly on OGR. My  
clients are configured to work on OGR whenever possible and only fall  
back to RC5 in case of network problems, so I have rarely done any RC5  
blocks. Accordingly, I had limits in proxyper.ini set like this:

[rc5-72]
minkeysready=5
maxkeysready=400
maxkeysdone=5

[ogrng]
minkeysready=34
maxkeysready=2400
maxkeysdone=34

Given my client settings, this resulted in proxy connecting to  
fullserver whenever it had 34 OGR blocks in its out-buffer, which was  
typically once in an hour or so.

Now that we are out of OGR work, all my clients started working on  
RC5, so I adjusted the buffer size settings accordingly:

[rc5-72]
minkeysready=100
maxkeysready=7200
maxkeysdone=100

However, this does not have the desired effect. Instead of waiting  
until 100 blocks have been gathered in the rc5 out-buffer, the proxy  
connects to upstream server every couple of minutes when it has only  
few RC5 blocks to return:

$ grep "Last uplink" console20140218.log

2014-02-18 00:09:40,Status: rc5-72: Last uplink sent 2 and received 0
2014-02-18 00:09:40,Status: ogrng: Last uplink sent 0 and received 0
2014-02-18 00:12:59,Status: rc5-72: Last uplink sent 5 and received 0
2014-02-18 00:12:59,Status: ogrng: Last uplink sent 0 and received 0
2014-02-18 00:15:40,Status: rc5-72: Last uplink sent 2 and received 0
2014-02-18 00:15:40,Status: ogrng: Last uplink sent 0 and received 0
2014-02-18 00:18:42,Status: rc5-72: Last uplink sent 6 and received 0
2014-02-18 00:18:42,Status: ogrng: Last uplink sent 0 and received 0
... etc

I modified the configuration of my personal proxy this morning and  
thought that maybe it needs some time to "settle in", but 12 hours  
later the situation seems unchanged. I don't want to DoS the upstream  
keyservers with my constant connection attempts, but I don't know how  
to stop this. I tried adding 'expertmode=1' to the [rc5-72] section,  
but this doesn't help.

--

-- 
Toomas Aas
participant #32,484
_______________________________________________
rc5 mailing list
rc5@...
http://lists.distributed.net/mailman/listinfo/rc5

Andrew Hime | 15 Feb 11:10 2014
Picon
Picon

still not there yet? *sigh*

proxy1.kl.my kiddo 12.5m 350 3.0w 52,310.36 62221/0 asia jp

And to think, someone got mad at me for hoarding OGR packets. All 256 of them.
_______________________________________________
rc5 mailing list
rc5@...
http://lists.distributed.net/mailman/listinfo/rc5
Andrew Hime | 13 Feb 07:11 2014
Picon
Picon

"are we there yet?" "juuust a little further..."

It's been a long time since we've finished a project, so it's kind of exciting to look at. Anybody from dnet able to give us an update on where we are?
_______________________________________________
rc5 mailing list
rc5@...
http://lists.distributed.net/mailman/listinfo/rc5
Greg Childers | 18 Jan 11:53 2014

CUDA clients need recompiling for newer GPUs

Hi,

The newer CUDA sm_35 GPUs such as the GTX Titan and Tesla K20/K40 have a funnel shift instruction, which can be used as a 32-bit rotate.  No code changes are necessary.  The compiler recognizes the two shifts and or as a rotate, and does the right thing.  Here are the results of my testing on a Tesla K20.

Current client:

dnetc v2.9108-517-CTR-10070312 for CUDA 3.1 on Linux (Linux 2.6.32-279.14.1 ...

Please provide the *entire* version descriptor when submitting bug reports.

The distributed.net bug report pages are at http://bugs.distributed.net/


[Jan 18 10:47:30 UTC] RC5-72: using core #0 (CUDA 1-pipe 64-thd).

[Jan 18 10:47:37 UTC] RC5-72: Benchmark for core #0 (CUDA 1-pipe 64-thd)

                      0.00:00:04.63 [937,151,615 keys/sec]

[Jan 18 10:47:37 UTC] RC5-72: using core #1 (CUDA 1-pipe 128-thd).

[Jan 18 10:47:44 UTC] RC5-72: Benchmark for core #1 (CUDA 1-pipe 128-thd)

                      0.00:00:04.44 [976,631,543 keys/sec]

[Jan 18 10:47:44 UTC] RC5-72: using core #2 (CUDA 1-pipe 256-thd).

[Jan 18 10:47:50 UTC] RC5-72: Benchmark for core #2 (CUDA 1-pipe 256-thd)

                      0.00:00:04.42 [981,795,666 keys/sec]

[Jan 18 10:47:50 UTC] RC5-72: using core #3 (CUDA 2-pipe 64-thd).

[Jan 18 10:47:57 UTC] RC5-72: Benchmark for core #3 (CUDA 2-pipe 64-thd)

                      0.00:00:04.74 [914,549,002 keys/sec]

[Jan 18 10:47:57 UTC] RC5-72: using core #4 (CUDA 2-pipe 128-thd).

[Jan 18 10:48:04 UTC] RC5-72: Benchmark for core #4 (CUDA 2-pipe 128-thd)

                      0.00:00:04.58 [948,142,344 keys/sec]

[Jan 18 10:48:04 UTC] RC5-72: using core #5 (CUDA 2-pipe 256-thd).

[Jan 18 10:48:10 UTC] RC5-72: Benchmark for core #5 (CUDA 2-pipe 256-thd)

                      0.00:00:04.40 [985,609,646 keys/sec]

[Jan 18 10:48:10 UTC] RC5-72: using core #6 (CUDA 4-pipe 64-thd).

[Jan 18 10:48:17 UTC] RC5-72: Benchmark for core #6 (CUDA 4-pipe 64-thd)

                      0.00:00:04.51 [962,502,541 keys/sec]

[Jan 18 10:48:17 UTC] RC5-72: using core #7 (CUDA 4-pipe 128-thd).

[Jan 18 10:48:23 UTC] RC5-72: Benchmark for core #7 (CUDA 4-pipe 128-thd)

                      0.00:00:04.40 [986,996,612 keys/sec]

[Jan 18 10:48:23 UTC] RC5-72: using core #8 (CUDA 4-pipe 256-thd).

[Jan 18 10:48:30 UTC] RC5-72: Benchmark for core #8 (CUDA 4-pipe 256-thd)                                                                                                           

                      0.00:00:04.36 [995,250,114 keys/sec]

[Jan 18 10:48:30 UTC] RC5-72: using core #9 (CUDA 1-pipe 64-thd busy wait).

[Jan 18 10:48:36 UTC] RC5-72: Benchmark for core #9 (CUDA 1-pipe 64-thd busy wait)                                                                                                  

                      0.00:00:04.53 [957,125,645 keys/sec]

[Jan 18 10:48:36 UTC] RC5-72: using core #10 (CUDA 1-pipe 64-thd sleep 100us).

[Jan 18 10:48:43 UTC] RC5-72: Benchmark for core #10 (CUDA 1-pipe 64-thd sleep 100us)                                                                                               

                      0.00:00:04.58 [947,487,144 keys/sec]

[Jan 18 10:48:43 UTC] RC5-72: using core #11 (CUDA 1-pipe 64-thd sleep dynamic).

[Jan 18 10:48:50 UTC] RC5-72: Benchmark for core #11 (CUDA 1-pipe 64-thd sleep dynamic)                                                                                             

                      0.00:00:04.57 [949,532,041 keys/sec]

[Jan 18 10:48:50 UTC] RC5-72 benchmark summary :

                      Default core : #0 (CUDA 1-pipe 64-thd)

                      Fastest core : #8 (CUDA 4-pipe 256-thd)


Recompiled client:

dnetc v2.9110-519-CTR-11072023 for CUDA on Linux (Linux 2.6.32-279.14.1.el6 ...

Please provide the *entire* version descriptor when submitting bug reports.

The distributed.net bug report pages are at http://bugs.distributed.net/


[Jan 18 10:50:19 UTC] RC5-72: using core #0 (CUDA 1-pipe 64-thd).

[Jan 18 10:50:24 UTC] RC5-72: Benchmark for core #0 (CUDA 1-pipe 64-thd)

                      0.00:00:03.19 [1,367,772,924 keys/sec]

[Jan 18 10:50:24 UTC] RC5-72: using core #1 (CUDA 1-pipe 128-thd).

[Jan 18 10:50:29 UTC] RC5-72: Benchmark for core #1 (CUDA 1-pipe 128-thd)

                      0.00:00:03.12 [1,395,317,272 keys/sec]

[Jan 18 10:50:29 UTC] RC5-72: using core #2 (CUDA 1-pipe 256-thd).

[Jan 18 10:50:35 UTC] RC5-72: Benchmark for core #2 (CUDA 1-pipe 256-thd)

                      0.00:00:03.09 [1,409,888,624 keys/sec]

[Jan 18 10:50:35 UTC] RC5-72: using core #3 (CUDA 2-pipe 64-thd).

[Jan 18 10:50:40 UTC] RC5-72: Benchmark for core #3 (CUDA 2-pipe 64-thd)

                      0.00:00:03.15 [1,383,760,581 keys/sec]

[Jan 18 10:50:40 UTC] RC5-72: using core #4 (CUDA 2-pipe 128-thd).

[Jan 18 10:50:45 UTC] RC5-72: Benchmark for core #4 (CUDA 2-pipe 128-thd)

                      0.00:00:03.04 [1,435,289,273 keys/sec]

[Jan 18 10:50:45 UTC] RC5-72: using core #5 (CUDA 2-pipe 256-thd).

[Jan 18 10:50:50 UTC] RC5-72: Benchmark for core #5 (CUDA 2-pipe 256-thd)

                      0.00:00:03.00 [1,454,768,816 keys/sec]

[Jan 18 10:50:50 UTC] RC5-72: using core #6 (CUDA 4-pipe 64-thd).

[Jan 18 10:50:55 UTC] RC5-72: Benchmark for core #6 (CUDA 4-pipe 64-thd)

                      0.00:00:03.11 [1,402,262,966 keys/sec]

[Jan 18 10:50:55 UTC] RC5-72: using core #7 (CUDA 4-pipe 128-thd).

[Jan 18 10:51:00 UTC] RC5-72: Benchmark for core #7 (CUDA 4-pipe 128-thd)

                      0.00:00:03.08 [1,416,234,138 keys/sec]

[Jan 18 10:51:00 UTC] RC5-72: using core #8 (CUDA 4-pipe 256-thd).

[Jan 18 10:51:05 UTC] RC5-72: Benchmark for core #8 (CUDA 4-pipe 256-thd)                                                                                                           

                      0.00:00:03.05 [1,429,372,665 keys/sec]

[Jan 18 10:51:05 UTC] RC5-72: using core #9 (CUDA 1-pipe 64-thd busy wait).

[Jan 18 10:51:11 UTC] RC5-72: Benchmark for core #9 (CUDA 1-pipe 64-thd busy wait)                                                                                                  

                      0.00:00:03.14 [1,386,448,528 keys/sec]

[Jan 18 10:51:11 UTC] RC5-72: using core #10 (CUDA 1-pipe 64-thd sleep 100us).

[Jan 18 10:51:16 UTC] RC5-72: Benchmark for core #10 (CUDA 1-pipe 64-thd sleep 100us)                                                                                               

                      0.00:00:03.29 [1,324,972,176 keys/sec]

[Jan 18 10:51:16 UTC] RC5-72: using core #11 (CUDA 1-pipe 64-thd sleep dynamic).

[Jan 18 10:51:21 UTC] RC5-72: Benchmark for core #11 (CUDA 1-pipe 64-thd sleep dynamic)                                                                                             

                      0.00:00:03.18 [1,371,027,270 keys/sec]

[Jan 18 10:51:21 UTC] RC5-72 benchmark summary :

                      Default core : #0 (CUDA 1-pipe 64-thd)

                      Fastest core : #5 (CUDA 2-pipe 256-thd)


You can easily compile for all current architectures by removing the ptx and cubin lines, and compiling with

NVCC = /usr/local/cuda/bin/nvcc --generate-code arch=compute_10,code=sm_10 --generate-code arch=compute_20,code=sm_20 --generate-code arch=compute_30,code=sm_30 --generate-code arch=compute_35,code=sm_35

Greg

_______________________________________________
rc5 mailing list
rc5@...
http://lists.distributed.net/mailman/listinfo/rc5

Gmane