On Tue, 2009-12-08 at 16:04 +0100, Oleg Nesterov wrote: > The > problem is, this code was developed out-of-tree. That is why we would > like to merge it asap, then do other changes which could be easily > reviewed. > > Now, do you really mean we should throw out the working code, rewrite > it avoiding these barriers, and resubmit? Sure, everything is possible. > But this means another round of out-of-tree development with unclear > results.
Out-of-tree development is bad, it having taken lot of effort is no excuse for merging ugly. Now, I'm not against barriers at all, but code that is as barrier heavy as this, with such bad comments and no clear indication it was actually worth using so many barriers make me wonder. Barriers aren't free either, and having multiple such things in quick succession isn't nessecarily faster than a lock, but much less obvious.
