bug#7489: [coreutils] over aggressive threads in sort

2010-12-05 Thread Jim Meyering
Paul Eggert wrote: > On 11/29/2010 02:46 PM, Paul Eggert wrote: >> My current guess, by the way, >> is that it's not a bug that can be triggered: it's merely >> useless code that is harmless and can safely be removed. > > I removed it as part of the following series of cleanup > patches. These are

bug#6216: Feature request: Split -p

2010-12-05 Thread Pádraig Brady
On 18/05/10 23:36, Pádraig Brady wrote: > On 18/05/10 21:02, Rich Jones wrote: >> Hey guys! >> >> Been fighting with batch splitting lately, was wondering if anybody would be >> interested in having a split -p --parts feature. It would take an integer >> and try to split the file into that many par

bug#7568: stat 'i\i' shows 'i\\i'

2010-12-05 Thread jidanni
stat 'i\i' shows 'i\\i'. Backspaces in filenames are doubled. stat (GNU coreutils) 8.5

bug#7489: [coreutils] over aggressive threads in sort

2010-12-05 Thread Chen Guo
Hi Professor Eggert, On Fri, Dec 3, 2010 at 1:10 PM, Paul Eggert wrote: > On 12/03/10 12:18, Chen Guo wrote: > Either option (either switch to mutexes everywhere, or have the top-level > merge go to memory) should work.  Perhaps we should try both and benchmark > them. Test machine is 4 core

bug#7489: [coreutils] over aggressive threads in sort

2010-12-05 Thread Paul Eggert
On 12/05/2010 09:16 PM, Chen Guo wrote: > Before saying anything else, I should note that for mutexes, on 4 > threads 20% of the time there's a segfault on a seemingly innocuous > line in queue_insert (): > node->queued = true It does sound like mutexes are the way to go, and that this bug needs