if you have to run hdparm to get those values to be '1', then your kernel doesn't actually support it.
I could achieve the same values before I had UDMA support in my kernel my settingthem with hdparm as well, but it wasn't actually being used. Jeff On Thu, 2003-06-12 at 18:56, Jason 'vanRijn' Kasper wrote: > On Thu, 2003-06-12 at 18:44, Jeffrey Stedfast wrote: > > I also run XFS on my home desktop and until I recently rebuilt my kernel > > with UDMA support, any amount of disk I/O would bring my machine to its > > knees. > > > > *nod* > > > I suggest you make sure that your kernel has UDMA support built in. > > > > mine does. > > > a quick and dirty check might be to do (as root): > > > > /sbin/hdparm -c -d /dev/hda1 > > I have this in my startup script: > > hdparm -u 1 -a 8 -c 1 -d 1 -k 1 /dev/hda > > and I get this when it's run: > > IO_support = 1 (32-bit) > unmaskirq = 1 (on) > using_dma = 1 (on) > keepsettings = 1 (on) > readahead = 8 (on) > > =:/ > > Any other thoughts? =:) I'm leaning towards notzed's hypothesis of > many, many small temporary files being created, then growing in a big, > big way, then being deleted. > > > If you get something like the following output: > > > > /dev/hda1: > > IO_support = 0 (default 16-bit) > > using_dma = 0 (off) > > > > then this is what your problem is. After I rebuilt my kernel with UDMA > > support, I get: > > > > /dev/hda1: > > IO_support = 1 (32-bit) > > using_dma = 1 (on) > > > > or some such. this is what you want :-) > > > > Jeff -- Jeffrey Stedfast Evolution Hacker - Ximian, Inc. [EMAIL PROTECTED] - www.ximian.com _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
