paul Posted July 31, 2003 Report Share Posted July 31, 2003 trinity root # hdparm -tT /dev/hda /dev/hda: Timing buffer-cache reads: 636 MB in 2.00 seconds = 318.00 MB/sec Timing buffered disk reads: 18 MB in 3.12 seconds = 5.77 MB/sec trinity root # :-( trinity root # hdparm -d1 /dev/hda /dev/hda: setting using_dma to 1 (on) HDIO_SET_DMA failed: Operation not permitted using_dma = 0 (off) trinity root # :? there are no options in bios to turn on/off DMA but my bios reports udma66 when booting. I have this board http://www.giga-byte.com/MotherBoard/Produ...ts_GA-6VXD7.htm and a brand new seagate 120gig with 8mb cache here's a bit of my kernel config x x [*] PCI IDE chipset support x x x x [*] Generic PCI IDE Chipset Support x x x x [*] Sharing PCI IDE interrupts support x x x x [*] Generic PCI bus-master DMA support x x x x [ ] Boot off-board chipsets first support x x x x [ ] Force enable legacy 2.0.X HOSTS to use DMA x x x x [*] Use PCI DMA by default when available x x x x [ ] Enable DMA only for disks x x x x [ ] ATA Work(s) In Progress (EXPERIMENTAL) x x can anybody help? Quote Link to comment Share on other sites More sharing options...
aRTee Posted July 31, 2003 Report Share Posted July 31, 2003 What does /var/log/dmesg say? Is there any mention that your mobo chipset is or isn't supported? Does it mention dma, in the section where the hda hdb etc are configured/detected? Could you post that? I don't know your mobo but if it has one of the latest chipsets it may be that your current kernel doesn't support it. Quote Link to comment Share on other sites More sharing options...
pmpatrick Posted July 31, 2003 Report Share Posted July 31, 2003 Try: # hdparm -X66 d1 /dev/hda If hdparm can't pick up the dma mode from the bios, you have to specify the mode using the -X switch. I've never had to specify it, but it's worth a shot. Also, make sure plug 'n play is disabled in the bios. Quote Link to comment Share on other sites More sharing options...
paul Posted July 31, 2003 Author Report Share Posted July 31, 2003 hey guys ... I re-did my kernel last night, and included support for every possible IDE chipset .. (I had a look at the MDK9.0 kernel, nad this what they have done) I now have better results, but not that good. cached ~340 read ~35 I will post my DMA stuff from dmesg when I get home tonight. but from memory it VIA vc68XXXX Quote Link to comment Share on other sites More sharing options...
pmpatrick Posted August 1, 2003 Report Share Posted August 1, 2003 I think your there. Here are my three drives and there all ultra 100: [root@localhost patrick]# hdparm -tT /dev/hdf /dev/hdf: Timing buffer-cache reads: 128 MB in 0.35 seconds =365.71 MB/sec Timing buffered disk reads: 64 MB in 1.60 seconds = 40.00 MB/sec [root@localhost patrick]# hdparm -tT /dev/hdg /dev/hdg: Timing buffer-cache reads: 128 MB in 0.37 seconds =345.95 MB/sec Timing buffered disk reads: 64 MB in 1.59 seconds = 40.25 MB/sec [root@localhost patrick]# hdparm -tT /dev/hde /dev/hde: Timing buffer-cache reads: 128 MB in 0.37 seconds =345.95 MB/sec Timing buffered disk reads: 64 MB in 1.59 seconds = 40.25 MB/sec [root@localhost patrick]# hdparm /dev/hdf /dev/hdf: multcount = 16 (on) IO_support = 3 (32-bit w/sync) unmaskirq = 0 (off) using_dma = 1 (on) keepsettings = 0 (off) readonly = 0 (off) readahead = 8 (on) geometry = 9732/255/63, sectors = 156355584, start = 0 All three drives have identical settings. Quote Link to comment Share on other sites More sharing options...
aRTee Posted August 2, 2003 Report Share Posted August 2, 2003 35MB/s is not that bad?? I get 40 with a 1 year old maxtor, 56 with a brandnew one... Quote Link to comment Share on other sites More sharing options...
bvc Posted August 2, 2003 Report Share Posted August 2, 2003 What effects the cached readings exactly? I only get cached =290 disk =36 It's a 1.5 year old 30GB 7200rpm maxtor. /dev/hda: multcount = 16 (on) IO_support = 3 (32-bit w/sync) unmaskirq = 1 (on) using_dma = 1 (on) keepsettings = 0 (off) readonly = 0 (off) readahead = 32 (on) geometry = 3736/255/63, sectors = 60030432, start = 0 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 Quote Link to comment Share on other sites More sharing options...
Germ Posted August 3, 2003 Report Share Posted August 3, 2003 5T030H3 Maxtor: /dev/hda: Timing buffer-cache reads: 128 MB in 0.54 seconds =237.04 MB/sec Timing buffered disk reads: 64 MB in 1.85 seconds = 34.59 MB/sec /dev/hda: multcount = 16 (on) IO_support = 1 (32-bit) unmaskirq = 1 (on) using_dma = 1 (on) keepsettings = 0 (off) readonly = 0 (off) readahead = 8 (on) geometry = 3736/255/63, sectors = 60030432, start = 0 Quote Link to comment Share on other sites More sharing options...
bvc Posted August 3, 2003 Report Share Posted August 3, 2003 I also have the 5T030H3 /dev/hda: Timing buffer-cache reads: 128 MB in 0.43 seconds =297.67 MB/sec Timing buffered disk reads: 64 MB in 1.80 seconds = 35.56 MB/sec My readahead=32 yours =8 I also max my accoustic setting to 254.....the default is 192. Quote Link to comment Share on other sites More sharing options...
paul Posted August 3, 2003 Author Report Share Posted August 3, 2003 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 bvc... how do I go about getting these setting ??? I know I can "hdparm -X68 /dev/hda" but how do I find out what it is using now? Quote Link to comment Share on other sites More sharing options...
bvc Posted August 3, 2003 Report Share Posted August 3, 2003 hdparm -I /dev/hdx hdparm -i /dev/hdx Quote Link to comment Share on other sites More sharing options...
aRTee Posted August 3, 2003 Report Share Posted August 3, 2003 Since we're at it: hdparm -tT /dev/hda /dev/hda: Timing buffer-cache reads: 128 MB in 0.51 seconds =250.98 MB/sec Timing buffered disk reads: 64 MB in 1.79 seconds = 35.75 MB/sec # hdparm -tT /dev/hdb /dev/hdb: Timing buffer-cache reads: 128 MB in 0.54 seconds =237.04 MB/sec Timing buffered disk reads: 64 MB in 1.14 seconds = 56.14 MB/sec Strange, I'm sure I used to have 40MB/s on hda before adding hdb.... bvc, what makes the difference in cached reads is mainly the chipset,... I know I have an 'older' via kt333 chipset, with less bandwidth between the north and southbridge (first version of Via's so called V-link). The cache on the hd doesn't make much difference; the one on my hda is 2MB, on my hdb there's 8MB of cache.. BTW Paul, the /var/log/dmesg also tells you which mode is used upon booting, this may help to know if your system sets itself up properly. Quote Link to comment Share on other sites More sharing options...
Germ Posted August 3, 2003 Report Share Posted August 3, 2003 Mine is different each time......... Today it's: /dev/hda: Timing buffer-cache reads: 128 MB in 0.57 seconds =224.56 MB/sec Timing buffered disk reads: 64 MB in 1.87 seconds = 34.22 MB/sec bvc, I'm going to try the readahead=32 :wink: I turned acoustic management off, supposedly that gives the fastest file read/write according to Maxtor. Quote Link to comment Share on other sites More sharing options...
Germ Posted August 3, 2003 Report Share Posted August 3, 2003 [root@grendel germ]# hdparm -c3 -A1 -m16 -d1 /dev/hda /dev/hda: setting 32-bit IO_support flag to 3 setting multcount to 16 setting using_dma to 1 (on) setting drive read-lookahead to 1 (on) multcount = 16 (on) IO_support = 3 (32-bit w/sync) using_dma = 1 (on) [root@grendel germ]# hdparm -Tt /dev/hda /dev/hda: Timing buffer-cache reads: 128 MB in 0.51 seconds =250.98 MB/sec Timing buffered disk reads: 64 MB in 1.88 seconds = 34.04 MB/sec so far, this is the best I've done. setting readahead to 32 actually slowed it down. :shock: [/code] Quote Link to comment Share on other sites More sharing options...
bvc Posted August 3, 2003 Report Share Posted August 3, 2003 Germ, how did you turn accoustical mgnt off? I figured setting it to 254 -M254 was basically turning it off. :? Thanks aRTee for the cache explanation! I have the via kt400. Makes me wonder what chipset those that are getting 318, 340, 365 have :? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.