Archives Discussions

[gaurav_garg]

Hi All,

If you are facing any problem of slowdown after calling multiple kernels. These issues can be resolved if you call error() on output stream after kernel call.

// Test case to generate slowdown
for(int i = 0; i < 100000; ++i)
{
    kernelCall(output);
}

// Workaround
for(int i = 0; i < 100000; ++i)
{
    kernelCall(output);
    output.error(); // Call error on output stream
}

[jean-claude]

Could this be a workaround for the infamous kernel multiloop blue screen too?

http://forums.amd.com/devforum/messageview.cfm?catid=328&threadid=104937&enterthread=y

JC

[gaurav_garg]

Probably not, It causes page trashing but nothing that can create issues at CAL or driver level.

[jean-claude]

Just for your info, I moved from Brook to CAL (using the same kernels) and this multiloop kernel generated blue screen doesn't occur anymore.

I suspect that some memory release are not completed properly in the brook version... who knows!?

BTW. Using a mixture of CAL and Brook is quite convenient, I think this gives better control to overall performances.

Cheers

Jean-Claude