Comment 20 for bug 929941

Revision history for this message
Stefan Bader (smb) wrote : Re: Kernel deadlock in scheduler on m2.{2,4}xlarge EC2 instance

Yes, this value is used right now. The question was whether this could be moved by now (depending on the AWS rollout status). But anyway, I changed the patch to activate ticket spinlocks even when compiled for 3.0.2 or higher. Which is what we would be the same situation we have right now, just with the code fixes.
Please give those v3 kernels some testing and let me know how those are behaving. Thanks.