another 3% mining increase with poclbm kernel.cl

[xanatos]

On my 5870 it jumped 16 mh from 385 to 401. I'm using the poclbm "old" kernel + the other +3% patch (that gives me only 1% of speedup :-( )

Weird, what's the rest of your setup? I've listed mine above and this mod decreases my performance on every 5870 I have tried, mix of ubuntu/windows, ati versions & sdk.

I have a single card, clocked 300/900 on Windows and Catalyst 11.5 (too lazy to install 11.6 and I've read that they don't change anything) and I'm using -w 256. Someone had a big difference on the other patch. I got only a 1%. Perhaps the trick is in the ratio of memory clock/process clock.

[zimpixa]

Actually 1MHash per card less (POCLBM with Ma() mod)

[phelix]

couple of sapphire hd 5850 xtremes

hard to tell if it does anything good.

lots of kernel errors on one of the cards. crashed with vpu recover after a couple of minutes.

[xarly1]

This method actually caused a decrease of 30%. I went from 26.81 MHash/s down to 18.71 MHash/s.

I have used this with a Radeon 5830 card. from 305MH/s to 315Mh/s
Here's some proof.


new kernel
http://imgur.com/JcMmZ

old kernel
http://imgur.com/YrRuL

what values clock/mem/voltage u have in ur card?

[DiabloD3]

I am locking this topic.

As per OpenCL specification:

6.5.2 __local (or local)
The __local or local address space name is used to describe variables that need to be
allocated in local memory and are shared by all work-items of a work-group. This qualifier can
be used with arguments to functions (including __kernel functions) declared as pointers, or
with variables declared inside a __kernel function.

6.5.4 __private (or private)
All variables inside a function (including __kernel functions), or passed into the function as
arguments are in the __private or private address space. Variables declared as pointers
are considered to point to the __private address space if an address space qualifier is not
specified except for arguments declared to be of type image2d_t and image3d_t which
implicitly point to the __global address space.

In other words, the hardware threads are stomping each others work and producing nonsense.