[lkml]   [2010]   [Mar]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Bugme-new] [Bug 15618] New: 2.6.18->2.6.32->2.6.33 huge regression in performance
Tomorrow I will try to patch and check 2.6.33 and see are this patches enough to restore performance or not, because on 2.6.33 kernel performance issue also used to involve somehow crgoup business (and performance was terrible even comparing to broken 2.6.32). If it will not fix 2.6.33, then I will ask to reopen the bug, otherwise I will post to stable@.

Thanks again for help,

On Mar 24, 2010, at 12:04 AM, Linus Torvalds wrote:

> On Tue, 23 Mar 2010, Anton Starikov wrote:
>> I think we got a winner!
>> Problem seems to be fixed.
>> Just for record, I used next patches:
>> 59c33fa7791e9948ba467c2b83e307a0d087ab49
>> 5d0b7235d83eefdafda300656e97d368afcafc9a
>> 1838ef1d782f7527e6defe87e180598622d2d071
>> 4126faf0ab7417fbc6eb99fb0fd407e01e9e9dfe
>> bafaecd11df15ad5b1e598adc7736afcd38ee13d
>> 0d1622d7f526311d87d7da2ee7dd14b73e45d3fc
> Ok. If you have performance numbers for before/after these patches for
> your actual workload, I'd suggest posting them to, and
> maybe those rwsem fixes will get back-ported.
> The patches are pretty small, and should be fairly safe. So they are
> certainly stable material.
> Linus

 \ /
  Last update: 2010-03-24 00:21    [W:0.080 / U:3.576 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site