CCminer(SP-MOD) Modded GPU kernels.

[pallas]

Pushed a 20% faster shavite_final implementation to github. Another #include "cuda_x11_aes_sp.cuh" modification...

The sp-modded Optimized AES has been applied to the following hashing functions.

echo  (done)
fugue (done)
shavite (only the final function / if shavite is the last algo in the chain)
whirlpool(not done)
streborg(not done)

Streebog can only fit 2 (3) copies of the tables in shared mem, unless you can compute them on fly. Did you manage to apply the "trick" to it?

[sp_]

Streebog can only fit 2 (3) copies of the tables in shared mem, unless you can compute them on fly. Did you manage to apply the "trick" to it?

The streebog opensource implementation use 8kb of shared memory. and the pascal chip has 96kb of shared memory. But you have some limitations.  I see that the cryptodredge 0.9 is using 48kb shared memory. You can use more shared memory if you disable the level1 cache..

[pallas]

Streebog can only fit 2 (3) copies of the tables in shared mem, unless you can compute them on fly. Did you manage to apply the "trick" to it?

The streebog opensource implementation use 8kb of shared memory. and the pascal chip has 96kb of shared memory. But you have some limitations.  I see that the cryptodredge 0.9 is using 48kb shared memory. You can use more shared memory if you disable the level1 cache..

256 X 8 X 8 = 16K
You can use up to 48k of shared mem so 2 or 3 copies.
As for pascal, "The maximum shared memory per block remains limited at 48KB as with prior architectures".

[sp_]

Thanks - your contributions have made it easier for even a relative novice to make further modifications to the code and come out (slightly) ahead of enemy and trex, even before their fees.

Convert simd to use shared memory instead of a big memory buffer  (d_temp4[thr_id]) and then you get a good speedup. this has already been done in the other private miners. I might opensource later on..

here from enemy  1.20 SIMD implementation disassembly converted to ptx

enemy 1,20 is using 16kb of sharedmem

Code:

..
st.shared.u32 [%r1671], %r1666;
shfl.sync.up.b32 %r1672|%p370, %r162, %r304, %r1653, %r302;
selp.b32	%r1673, %r144, %r1672, %p92;
shfl.sync.up.b32 %r1674|%p371, %r154, %r304, %r1653, %r302;
selp.b32	%r1675, %r136, %r1674, %p92;
mul.lo.s32 %r1676, %r1673, 185;
mul.lo.s32 %r1677, %r1675, 185;
prmt.b32 %r1678, %r1676, %r1677, %r1661;
shfl.sync.idx.b32 %r1679|%p372, %r1678, %r1665, %r301, %r302;
st.shared.u32 [%r1671+4], %r1679;
shfl.sync.up.b32 %r1680|%p373, %r126, %r304, %r1653, %r302;
selp.b32	%r1681, %r108, %r1680, %p92;
shfl.sync.up.b32 %r1682|%p374, %r118, %r304, %r1653, %r302;
selp.b32	%r1683, %r100, %r1682, %p92;
mul.lo.s32 %r1684, %r1681, 185;
mul.lo.s32 %r1685, %r1683, 185;
prmt.b32 %r1686, %r1684, %r1685, %r1661;
shfl.sync.idx.b32 %r1687|%p375, %r1686, %r1665, %r301, %r302;
st.shared.u32 [%r1671+8], %r1687;
shfl.sync.up.b32 %r1688|%p376, %r1613, %r304, %r1653, %r302;
selp.b32	%r1689, %r180, %r1688, %p92;
shfl.sync.up.b32 %r1690|%p377, %r190, %r304, %r1653, %r302;
selp.b32	%r1691, %r172, %r1690, %p92;
mul.lo.s32 %r1692, %r1689, 185;
mul.lo.s32 %r1693, %r1691, 185;
prmt.b32 %r1694, %r1692, %r1693, %r1661;
shfl.sync.idx.b32 %r1695|%p378, %r1694, %r1665, %r301, %r302;
st.shared.u32 [%r1671+12], %r1695;
shfl.sync.up.b32 %r1696|%p379, %r91, %r304, %r1653, %r302;
selp.b32	%r1697, %r73, %r1696, %p92;
shfl.sync.up.b32 %r1698|%p380, %r3433, %r304, %r1653, %r302;
selp.b32	%r1699, %r3432, %r1698, %p92;
mul.lo.s32 %r1700, %r1697, 185;
mul.lo.s32 %r1701, %r1699, 185;
prmt.b32 %r1702, %r1700, %r1701, %r1661;
ld.const.u8 %r1703, [%r1664+8];
shfl.sync.idx.b32 %r1704|%p381, %r1702, %r1703, %r301, %r302;
st.shared.u32 [%r1671+128], %r1704;
...

[sp_]

"The maximum shared memory per block remains limited at 48KB as with prior architectures".

So you need 2 blocks.

[bensam1231]

If coin devs give two shits about the actual mining community (IE gpu miners), they really need to be more proactive with protecting their coins against ASICs and especially FPGAs. Changing things up on a regular schedule including forking at the first signs of ASICs to a new algo. There are more then enough GPU developers to keep up with evolving algos, especially after this year. More advanced ASICs are functioning more and more like GPUs (and FPGAs) to fill in the gap with evolving algos as well. Keep it fresh if you want to keep your community around. Not everyone is a BTC or ETH.

X16r/X16s/C11/x17 Spmod-git #11 has been released

- Added support for X17 (+10-15% faster than the ccminer alexis 1.0 opensource fork) (24-25MHASH on the 1080ti)
- Faster x16r/x16s +3-5% more than sp-mod #10 (Optimalizations added to Fugue, whirlpool)

this miner is free, opensource, and have no fee

cuda 9.2 builds:

https://github.com/sp-hash/suprminer/releases

sourcecode:

https://github.com/sp-hash/suprminer/commits/master

Your free product will not allow t-rex, Cryptodredge and Enemy sleep. Definitely we will see their new versions in a few days.

From what I've seen based on SPs updates, their miners (especially enemy) is updated about a day later with changes SP makes. Hence why open software doesn't go anywhere.

[Mr.Spider703]

with changes SP makes

if others took work SP_ and used it - the income on coins at SP_ would be higher. at the moment, SP_ mainers in the console draws well, but the income of coins loses to everyone else

[abudfv2008]

From what I've seen based on SPs updates, their miners (especially enemy) is updated about a day later with changes SP makes. Hence why open software doesn't go anywhere.

Enemy adopt sp_ "improvements" and release his miner that is faster than sp_ slow miner with all those "improvements".
Nice logic. 

For a person with normal logic it is evident that sp_ can't compete with z-enemy/t-rex miners and he make his "improvements" based on what z/t already implemented. That's why this miner is not sold as others - noone will by slow miner. That's why in this case sp_ decided to be a "knight in white clothes" and release slow but opensource miner. 

P.S. But anyway - it is good work from some point of view.

[sp_]

I don't earn any money from my opensource work, but my private bins are getting faster and faster.
X16R/X17 has improved to become +30% faster in a few months thanks to optimalizations. I made the 27MHASH x17 miner first..

Here is a post from August 8th. When enemy 1.14 and t-rex 5.7 was "the fastest"

Still 20% slower than Enemy?

My private is around 20% faster than (enemy 1.14)/(t-rex 5.7) in x16r/x16s/x17  27 MHASH x17 1080ti, (2BTC)

[abudfv2008]

I don't earn any money from my opensource work, but my private bins are getting faster and faster.
X16R/X17 has improved to become +30% faster in a few months thanks to optimalizations. I made the 27MHASH x17 miner first..

Here is a post from August 8th. When enemy 1.14 and t-rex 5.7 was "the fastest"

Still 20% slower than Enemy?

My private is around 20% faster than (enemy 1.14)/(t-rex 5.7) in x16r/x16s/x17  27 MHASH x17 1080ti, (2BTC)

We all know how you "measure".  27Mh was "on paper".  In reality maybe 23-24 was achieved.

[Mr.Spider703]

I don't earn any money from my opensource work, but my private bins are getting faster and faster.
X16R/X17 has improved to become +30% faster in a few months thanks to optimalizations. I made the 27MHASH x17 miner first..

Here is a post from August 8th. When enemy 1.14 and t-rex 5.7 was "the fastest"

Still 20% slower than Enemy?

My private is around 20% faster than (enemy 1.14)/(t-rex 5.7) in x16r/x16s/x17  27 MHASH x17 1080ti, (2BTC)

We all know how you "measure".  27Mh was "on paper".  In reality maybe 23-24 was achieved.

but for free

[sp_]

but for free

I have extracted all the kernels from the other devs and can soon publish a ptx opensource miner.. 30MHASH x17(asus 1080ti 90% tdp, +130 core +600 mem). 0.8% dev fee. Kernels made by t-rex/enemy/sp-mod. Thanks for the free work guys..

[abudfv2008]

I don't earn any money from my opensource work, but my private bins are getting faster and faster.
X16R/X17 has improved to become +30% faster in a few months thanks to optimalizations. I made the 27MHASH x17 miner first..

Here is a post from August 8th. When enemy 1.14 and t-rex 5.7 was "the fastest"

Still 20% slower than Enemy?

My private is around 20% faster than (enemy 1.14)/(t-rex 5.7) in x16r/x16s/x17  27 MHASH x17 1080ti, (2BTC)

We all know how you "measure".  27Mh was "on paper".  In reality maybe 23-24 was achieved.

but for free

What for free? Sp_ is talking about private miner. So 0.05BTC + dev fee that is mined at every start. So after each crash another devfee that is exactly in sp_ manner.

[@enemy]

but for free

I have extracted all the kernels from the other devs and can soon publish a ptx opensource miner.. 30MHASH x17(asus 1080ti 90% tdp, +130 core +600 mem). 0.8% dev fee. Kernels made by t-rex/enemy/sp-mod. Thanks for the free work guys..

Do not forget to rename everything - _sp and in a month write that we steal your code from you 

[sp_]

_sp and in a month write that we steal your code from you 

I don't steal code. I plan use your free code in you "free" miner and release the sourcecode with it. (the Ptx assembly code). Then  I won't violate the GPL licence you are violating. My miner will be faster,opensource, free and with a smaller devfee of 0.8%

[COBOK]

but for free

I have extracted all the kernels from the other devs and can soon publish a ptx opensource miner.. 30MHASH x17(asus 1080ti 90% tdp, +130 core +600 mem). 0.8% dev fee. Kernels made by t-rex/enemy/sp-mod. Thanks for the free work guys..

  you now confessed that you are stealing code from other developers, it's very bad

[sp_]

I have found evidence of my gpl code in their work. The sourcecode is provided for free in the public exefiles released by team cryptodregde/team enemy/team-t-rex (assembly language). My miner will be opensource and under GPL. The ptx kernels will be compiled runtime and executed by my program. If they release a faster miner, I will extract the new ptx code to make sure that my opensource miner always is the fastest.

[abudfv2008]

but for free

I have extracted all the kernels from the other devs and can soon publish a ptx opensource miner.. 30MHASH x17(asus 1080ti 90% tdp, +130 core +600 mem). 0.8% dev fee. Kernels made by t-rex/enemy/sp-mod. Thanks for the free work guys..

  you now confessed that you are stealing code from other developers, it's very bad

More than that - he confessed that he is incapable to make faster miner due to lack of skills. And the only option he has left is to steal kernels from cd/t-rex/enemy.

[sp_]

kernels from cd/t-rex/enemy.

The best from cd/t-rex/enemy kernels is only giving 28MHASH on the 1080ti (x17). So I add the profitable percent. The +10% the other guys can't copy..

[abudfv2008]

kernels from cd/t-rex/enemy.

The best from cd/t-rex/enemy kernels is only giving 28MHASH on the 1080ti (x17). So I add the profitable percent. The +10% the other guys can't copy..

blablabla. Do first than talk. Who knows - maybe when you will accomplish adadtation of stolen kernels then z/t will do 35Mh. Whats the problem to write code? Lack of knowledge and abilities, isn't it?
For the moment - your miner is the slowest, far behind z/t.
Pity for you, but your time has passed. There is no alexis78 to steal code from Stealing kernels won't help you - it's a dead end.