Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 26 Jul 2013 23:31:29 +0100
From: Rafael Waldo Delgado Doblas <lord.rafa@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Parallella: Litecoin mining

Hello,

2013/7/26 Rafael Waldo Delgado Doblas <lord.rafa@...il.com>

> V will be modified several times during the calculation and will need
> whole 32KB per core. Can I load the binary executable image in just one
> core memory area and run it from the rest of the cores?
>
> If we can do that the memory map will looks something like:
>
> 0-31K for V on first core
> 32-63K for V on second core
> ...
> 416-447K for V on fourteenth core
> 448-479K for V on fifteenth core
>
> 480-?? for binary executable image
> ??-??? for XY B first core.
> ....
> ??-??? for XY B fifteenth core.
>
> With this approach only 15 of 16 cores can be used because there is no
> memory for the sixteenth core.
>


In adition to my last mail, I read this

"With the scrypt parameters used in litecoin’s implementation (N = 1024; p
= 1; r = 1), each thread needs about 64-128 KB depending on the lookup_gap
and thread_concurrency settings when mining with a GPU" here
http://cryptocur.com/litecoin/

I need to find why there 64BK threads then I need to know what means
lookup_gap and thread_concurrency.

regards,
Rafa

Content of type "text/html" skipped

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.