Comment 6 for bug 493156

Please reconsider enabling CONFIG_TASK_DELAY_ACCT. Just because there is a slight penalty in some use cases doesn't motivate disabling it, when iotop and possibly other valuable tools are not working as they should. People that really need those extra milliseconds are usually better equipped when it comes to messing with kernel variables anyway, so why not keep it enabled by default and let them disable it.

At least provide some numbers for the actual penalty, preferrably with a test case attached, to motivate the decision. Just stating that CONFIG_TASK_DELAY_ACCT "causes a performance hit" is not good enough.