Horrible performance: hdparm

2006-07-11 Thread Osamu Aoki
Hi, On Sat, Jul 08, 2006 at 06:10:37PM -0400, Joey Hess wrote: Rich Johnson wrote: Judging from the lackadaisical disk LED activity, I doubt it's the disk. Disk issues can lead to apparently low disk activity in some situations, and it's the first thing I'd check: Make sure that DMA is on,

Re: Horrible performance: hdparm

2006-07-11 Thread Linas Žvirblis
Osamu Aoki wrote: What does people feel to make hdparm with DMA enabled to be default for etch? Is is not the kernel that needs to be tuned to enable/disable this by default? It also seems more reliable than simply brute-forcing this on. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a

Re: Horrible performance: hdparm

2006-07-11 Thread Henrique de Moraes Holschuh
On Wed, 12 Jul 2006, Osamu Aoki wrote: What does people feel to make hdparm with DMA enabled to be default for etch? Leave the DMA default for the kernel (hint: it is already on for disks, and unless we are compiling our kernels with the DMA only for disks option, also for ATAPI devices when

Re: Horrible performance: hdparm

2006-07-11 Thread Frans Pop
On Tuesday 11 July 2006 19:01, Henrique de Moraes Holschuh wrote: What you *can* do that would be helpful (and really, this would be best fixed in the kernel as well) is to set -u 1 by default, but don't change -d (dma). Please file a wishlist bugreport against debian-installer if you really

Re: Horrible performance: hdparm

2006-07-11 Thread Frans Pop
On Wednesday 12 July 2006 00:11, Frans Pop wrote: On Tuesday 11 July 2006 19:01, Henrique de Moraes Holschuh wrote: What you *can* do that would be helpful (and really, this would be best fixed in the kernel as well) is to set -u 1 by default, but don't change -d (dma). Please file a

Re: Horrible performance: hdparm

2006-07-11 Thread Joey Hess
Osamu Aoki wrote: Hi, On Sat, Jul 08, 2006 at 06:10:37PM -0400, Joey Hess wrote: Rich Johnson wrote: Judging from the lackadaisical disk LED activity, I doubt it's the disk. Disk issues can lead to apparently low disk activity in some situations, and it's the first thing I'd check: