View previous topic :: View next topic |
Author |
Message |
tba Apprentice
Joined: 01 Jun 2002 Posts: 173
|
Posted: Mon Jul 01, 2002 8:44 pm Post subject: assumind idebus=33mhz |
|
|
i get that message during boot.
my idebus is 100mhz so i override with idebus=100 but i dont see any performance increase. the only time my performance is bad is when i am searching for something (using kfind ) then it gets really choppy.
i have an athlon xp and a 40g WDC hard drive (last years model)
here are the results of hdparm /dev/hda
Code: |
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 = 4865/255/63, sectors = 78165360, start = 0
|
and here is the throughput test...
Code: |
Timing buffer-cache reads: 128 MB in 0.65 seconds =196.02 MB/sec
Timing buffered disk reads: 64 MB in 1.88 seconds = 34.02 MB/sec
|
"does that look right for a fairly new system" is my only question.
thanks in advance |
|
Back to top |
|
|
delta407 Bodhisattva
Joined: 23 Apr 2002 Posts: 2876 Location: Chicago, IL
|
Posted: Mon Jul 01, 2002 8:46 pm Post subject: |
|
|
200 MB/s across the IDE bus is quite good, as is 34 MB/s off the disk. You're fine.
For searching, put updatedb in your crontab somewhere; I think kfind can use the locate database if it's present, but I'm not sure. |
|
Back to top |
|
|
Naan Yaar Bodhisattva
Joined: 27 Jun 2002 Posts: 1549
|
Posted: Mon Jul 01, 2002 8:47 pm Post subject: Re: assumind idebus=33mhz |
|
|
Looks about right. My <1 year system tops out at about 32MB/sec from "hdparm -t".
tba wrote: | i get that message during boot.
my idebus is 100mhz so i override with idebus=100 but i dont see any performance increase. the only time my performance is bad is when i am searching for something (using kfind ) then it gets really choppy.
i have an athlon xp and a 40g WDC hard drive (last years model)
here are the results of hdparm /dev/hda
Code: |
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 = 4865/255/63, sectors = 78165360, start = 0
|
and here is the throughput test...
Code: |
Timing buffer-cache reads: 128 MB in 0.65 seconds =196.02 MB/sec
Timing buffered disk reads: 64 MB in 1.88 seconds = 34.02 MB/sec
|
"does that look right for a fairly new system" is my only question.
thanks in advance |
|
|
Back to top |
|
|
tba Apprentice
Joined: 01 Jun 2002 Posts: 173
|
Posted: Mon Jul 01, 2002 8:55 pm Post subject: thanks |
|
|
thanks again guys |
|
Back to top |
|
|
tba Apprentice
Joined: 01 Jun 2002 Posts: 173
|
Posted: Mon Jul 01, 2002 9:11 pm Post subject: updatedb |
|
|
i added updatedb to crontab but i have to say it looks out of place. ill know how out of place nectime i reboot . should i run it weekly? there is nothing in the /etc/cron.weekly/.list files. i notice if kfinds is running itllll take up 80%+ of my memory.... that cant be normal. |
|
Back to top |
|
|
delta407 Bodhisattva
Joined: 23 Apr 2002 Posts: 2876 Location: Chicago, IL
|
Posted: Mon Jul 01, 2002 10:18 pm Post subject: |
|
|
Hmmm... doesn't seem to use the locate database, nevermind. Guess you're screwed with KFind. |
|
Back to top |
|
|
Disquiet n00b
Joined: 14 Jun 2002 Posts: 48 Location: Christchurch, New Zealand
|
Posted: Mon Jul 01, 2002 10:52 pm Post subject: |
|
|
I think you guys have got the wrong idea about what idebus does...Here's a snippet from the kernel docs:
"idebus=xx" : inform IDE driver of VESA/PCI bus speed in MHz,
where "xx" is between 20 and 66 inclusive,
used when tuning chipset PIO modes.
For PCI bus, 25 is correct for a P75 system,
30 is correct for P90,P120,P180 systems,
and 33 is used for P100,P133,P166 systems.
If in doubt, use idebus=33 for PCI.
As for VLB, it is safest to not specify it.
Bigger values are safer than smaller ones.
So it would seem 33 is a good value, and 100 is a value outside the range...so probably doesn't do anything. |
|
Back to top |
|
|
tba Apprentice
Joined: 01 Jun 2002 Posts: 173
|
Posted: Mon Jul 01, 2002 11:30 pm Post subject: |
|
|
Disquite,
idebus=66 doesnt help hdparm -tT either but i guess ill put it in rc.start anyway... |
|
Back to top |
|
|
Sesquipedalian n00b
Joined: 22 May 2002 Posts: 62 Location: Loveland, CO
|
Posted: Tue Jul 02, 2002 3:33 pm Post subject: |
|
|
33 is the correct value. Your IDE controller hangs off of the PCI bus which runs at 33 MHz. Unless you have a board with 66MHz/64-bit PCI bus and an IDE controller that uses it (I don't think there are any, that would just be silly), it is set properly.
- Sesq |
|
Back to top |
|
|
Malakin Veteran
Joined: 14 Apr 2002 Posts: 1692 Location: Victoria BC Canada
|
Posted: Tue Jul 02, 2002 6:39 pm Post subject: |
|
|
You're mixing up the ata speed with the ide bus frequency. As was already said your ide bus does indeed run at 33mhz.
Type this "hdparm -i /dev/hda" and it will tell you what udma mode you're using.
udma2 = ata33 = "hdparm -X66 /dev/hda"
udma4 = ata66 = "hdparm -X68 /dev/hda"
udma5 = ata100 = "hdparm -X69 /dev/hda"
udma6 = ata133 = "hdparm -X70 /dev/hda"
An 80 pin ide cable is required for modes past ata33.
The kernel should automatically choose the highest setting available for your setup.
Anything past ata66 won't make any differnece unless you have an unusual setup, raid striping for example. |
|
Back to top |
|
|
|