|
hdparm 优化硬盘的配置
4, Speeding up Linux Using hdparm.. 15 需要配置的原因是硬盘不断更新换代,而linux系统为了兼容和稳定,默认没有采用较新的硬盘技术. 俺们的流媒体服务器配置: 分别为采用32位模式,响应其他中断,打开DMA模式,最后一个是扇区,估计是因为采用了自己的文件系统,内部有优化,所以关闭这个特性 -X因为大多数/全部现代 IDE 驱动器默认它们最快的 PIO 传输模式为打开. 所以摆弄它是没有必要的也是冒险的. 比较有用的参数如下: Hdparm命令的一些常用的其他参数功能 -g 显示硬盘的磁轨，磁头，磁区等参数。 -i 显示硬盘的硬件规格信息，这些信息是在开机时由硬盘本身所提供。 -I 直接读取硬盘所提供的硬件规格信息。 -p 设定硬盘的PIO模式。 -Tt 评估硬盘的读取效率和硬盘快取的读取效率。 -u <0或1> 在硬盘存取时，允许其他中断要求同时执行。 -v 显示硬盘的相关设定。 尤其是 [root@ME_90_146 rss]# hdparm -Tt /dev/hda /dev/hda: Timing buffer-cache reads: 128 MB in 0.20 seconds =624.39 MB/sec Timing buffered disk reads: 64 MB in 1.39 seconds = 45.94 MB/sec [root@ME_90_146 rss]# [root@ME_90_146 rss]# hdparm /dev/hda /dev/hda: multcount = 0 (off) IO_support = 3 (32-bit w/sync) unmaskirq = 1 (on) using_dma = 1 (on) keepsettings = 0 (off) readonly = 0 (off) readahead = 8 (on) geometry = 30401/255/63, sectors = 488397168, start = 0
使用hdparm改善Linux系统性能 如果你的Linux系统运行于IDE硬盘，可以使用hdparm工具来提高磁盘I/O的性能。不过使用hdparm要小心，因为可能破坏硬盘上的数据。所以在使用hdparm之前，仔细阅读你的硬盘手册。根据你具体的硬盘规格来使用相应的hdparm开关参数。对一块UltraATA/66 EIDE 硬盘，其控制芯片支持多 PIO 模式和DMA，我们使用以下命令来调谐磁盘性能： # /sbin/hdparm -x66 -d1 -u1 -m16 -c3 /dev/hda 选项说明： ① c3 ：就是把硬盘的16位格式转换为32位模式（32-bit mode w/sync）。控制数据如何从pci总线传递到控制器。 ② m16 ：改变硬盘的多路扇区的读功能，-m16可以使得硬盘在一次i/o中断中读入16个扇区的数据（据具体硬盘而定）。 ③ d1：打开DMA模式。 ④ x66 ：在支持UDMA-capable的硬盘中，这个参数可以支持双DMA通道的数据传输模式。 ⑤ u1 ：Linux在处理磁盘中断时，可以unmask其他的中断或者响应其他中断相关的任务。 查看以上的更改情况可以使用命令： # /sbin/hdparm /dev/hda 测试磁盘I/O性能可以使用命令： # /sbin/hdparm -tT /dev/hda 如果磁盘的性能有改进的话，可以使用以下命令来保存设置： # /sbin/hdparm -k1 /dev/had 2,中文手册:
hdparm 文档 http://www./bbs/printthread.php?t=210179 hdparm - 获取/设置硬盘参数 3,英文手册:
http://wiki./index.php?title=Hdparm&variant=zh-cn Linux命令：hdparm 功能说明：显示与设定硬盘的参数。 语 法：hdparm [-CfghiIqtTvyYZ][-a <快取分区>][-A <0或1>][-c ][-d <0或1>][-k <0或1>][-K <0或1>][-m <分区数>][-n <0或1>][-p ][-P <分区数>][-r <0或1>][-S <时间>][-u <0或1>][-W <0或1>][-X <传输模式>][设备] 补充说明：hdparm可检测，显示与设定IDE或SCSI硬盘的参数。 参 数： -a<快取分区> 设定读取文件时，预先存入块区的分区数，若不加上<快取分区>选项，则显示目前的设定。 -A<0或1> 启动或关闭读取文件时的快取功能。 -c 设定IDE32位I/O模式。 -C 检测IDE硬盘的电源管理模式。 -d<0或1> 设定磁盘的DMA模式。 -f 将内存缓冲区的数据写入硬盘，并清楚缓冲区。
-g 显示硬盘的磁轨，磁头，磁区等参数。
-h 显示帮助。
-i 显示硬盘的硬件规格信息，这些信息是在开机时由硬盘本身所提供。
-I 直接读取硬盘所提供的硬件规格信息。
-k<0或1> 重设硬盘时，保留-dmu参数的设定。 -K<0或1> 重设硬盘时，保留-APSWXZ参数的设定。 -m<磁区数> 设定硬盘多重分区存取的分区数。 -n<0或1> 忽略硬盘写入时所发生的错误。 -p 设定硬盘的PIO模式。 -P<磁区数> 设定硬盘内部快取的分区数。 -q 在执行後续的参数时，不在屏幕上显示任何信息。
-r<0或1> 设定硬盘的读写模式。 -S<时间> 设定硬盘进入省电模式前的等待时间。 -t 评估硬盘的读取效率。
-T 平谷硬盘快取的读取效率。
-u<0或1> 在硬盘存取时，允许其他中断要求同时执行。 -v 显示硬盘的相关设定。
-W<0或1> 设定硬盘的写入快取。 -X<传输模式> 设定硬盘的传输模式。 -y 使IDE硬盘进入省电模式。 -Y 使IDE硬盘进入睡眠模式。 -Z 关闭某些Seagate硬盘的自动省电功能。
NAME hdparm - get/set hard disk parameters SYNOPSIS hdparm [ -a [sectcount] ] [ -A [0|1] ] [ -c [chipset_mode] ] [ -C ] [ -d [0|1] ] [ -f ] [ -g ] [ -i ] [ -k [0|1] ] [ -K [0|1] ] [ -L [0|1] ] [ -m [sectcount] ] [ -p [0|1|2|3|4|5] ] [ -P [sectcount] ] [ -q ] [ -r [0|1] ] [ -S [timeout] ] [ -T ] [ -t ] [ -u [0|1] ] [ -v ] [ -W [0|1] ] [ -X [xfermode] ] [ -y ] [ -Y ] [ -Z ] [device] .. DESCRIPTION hdparm provides a command line interface to various hard disk ioctls supported by the stock Linux IDE/ST-506 device driver. This utility requires Linux kernel version OPTIONS When no flags are given, -acdgkmnru is assumed (except when a given device is SCSI or an old XT-type MFM/RLL, in which cases -gr and -adgr are the defaults, respectively). -a Get/set sector count for filesystem read-ahead. This is used to improve performance in sequen? tial reads of large files, by prefetching additional blocks in anticipation of them being needed by the running task. In the current kernel version ( -A Disable/enable the IDE drives read-lookahead feature (usually ON by default). -c Query/enable (E)IDE 32-bit I/O support. A numeric parameter can be used to enable/disable 32-bit I/O support: Currently supported values include 0 to disable 32-bit I/O support, 1 to enable 32-bit data transfers, and 3 to enable 32-bit data transfers with a special sync sequence required by many chipsets. The value 3 works with nearly all 32-bit IDE chipsets, but incurs slightly more overhead. Note that "32-bit" refers to data transfers across a PCI or VLB bus to the interface card only; all (E)IDE drives still have only a 16-bit connection over the ribbon cable from the interface card. -C Check the current IDE power mode status, which will always be one of unknown (drive does not sup? port this command), active/idle (normal operation), standby (low power mode, drive has spun down), or sleeping (lowest power mode, drive is completely shut down). The -S, -y, -Y, and -Z flags can be used to manipulate the IDE power modes. -d Disable/enable the "using_dma" flag for this drive. This option only works with a few combina? tions of drives and interfaces which support DMA and which are known to the IDE driver (and with all supported XT interfaces). In particular, the Intel Triton chipset is supported for bus-mas? tered DMA operation with many drives (experimental). It is also a good idea to use the -X34 option in combination with -d1 to ensure that the drive itself is programmed for multiword DMA mode2. Using DMA does not necessarily provide any improvement in throughput or system perfor? mance, but many folks swear by it. Your mileage may vary. -E Set cdrom speed. This is NOT necessary for regular operation, as the drive will automatically switch speeds on its own. But if you want to play with it, just supply a speed number after the option, usually a number like 2 or 4. -f Sync and flush the buffer cache for the device on exit. This operation is also performed as part of the -t and -T timings. -g Display the drive geometry (cylinders, heads, sectors), the size (in sectors) of the device, and the starting offset (in sectors) of the device from the beginning of the drive. -h Display terse usage information (help). -i Display the identification info that was obtained from the drive at boot time, if available. This is a feature of modern IDE drives, and may not be supported by older devices. The data returned may or may not be current, depending on activity since booting the system. However, the current multiple sector mode count is always shown. For a more detailed interpretation of the identification info, refer to AT Attachment Interface for Disk Drives (ANSI ASC X3T9.2 working draft, revision -I Request identification info directly from the drive, which is displayed in its raw form with no endian changes or corrections. Otherwise similar to the -i option. -k Get/set the keep_settings_over_reset flag for the drive. When this flag is set, the driver will preserve the -dmu options over a soft reset, (as done during the error recovery sequence). This flag defaults to off, to prevent drive reset loops which could be caused by combinations of -dmu settings. The -k flag should therefore only be set after one has achieved confidence in correct system operation with a chosen set of configuration settings. In practice, all that is typically necessary to test a configuration (prior to using -k) is to verify that the drive can be read/written, and that no error logs (kernel messages) are generated in the process (look in /var/adm/messages on most systems). -K Set the drives keep_features_over_reset flag. Setting this enables the drive to retain the set? tings for -APSWXZ over a soft reset (as done during the error recovery sequence). Not all drives support this feature. -L Set the drives doorlock flag. Setting this to will lock the door mechanism of some removeable hard drives (eg. Syquest, ZIP, Jazz..), and setting it to maintains the door locking mechanism automatically, depending on drive usage (locked whenever a filesystem is mounted). But on system shutdown, this can be a nuisance if the root partition is on a removeable disk, since the root partition is left mounted (read-only) after shutdown. So, by using this command to unlock the door -b after the root filesystem is remounted read-only, one can then remove the cartridge from the drive after shutdown. -m Get/set sector count for multiple sector I/O on the drive. A setting of 0 disables this feature. Multiple sector mode (aka IDE Block Mode), is a feature of most modern IDE hard drives, permit? ting the transfer of multiple sectors per I/O interrupt, rather than the usual one sector per interrupt. When this feature is enabled, it typically reduces operating system overhead for disk I/O by 30-50%. On many systems, it also provides increased data throughput of anywhere from 5% to 50%. Some drives, however (most notably the WD Caviar series), seem to run slower with multi? ple mode enabled. Your mileage may vary. Most drives support the minimum settings of 2, 4, 8, or 16 (sectors). Larger settings may also be possible, depending on the drive. A setting of 16 or 32 seems optimal on many systems. Western Digital recommends lower settings of 4 to 8 on many of their drives, due tiny (32kB) drive buffers and non-optimized buffering algorithms. The -i flag can be used to find the maximum setting supported by an installed drive (look for MaxMult? Sect in the output). Some drives claim to support multiple mode, but lose data at some settings. Under rare circumstances, such failures can result in massive filesystem corruption. -p Attempt to reprogram the IDE interface chipset for the specified PIO mode, or attempt to auto- tune for the "best" PIO mode supported by the drive. This feature is supported in the kernel for only a few "known" chipsets, and even then the support is iffy at best. Some IDE chipsets are unable to alter the PIO mode for a single drive, in which case this flag may cause the PIO mode for both drives to be set. Many IDE chipsets support either fewer or more than the standard six (0 to 5) PIO modes, so the exact speed setting that is actually implemented will vary by chipset/driver sophistication. Use with extreme caution! This feature includes zero protection for the unwary, and an unsuccessful outcome may result in severe filesystem corruption! -P Set the maximum sector count for the drives internal prefetch mechanism. Not all drives support this feature. -q Handle the next flag quietly, supressing normal output. This is useful for reducing screen clut? ter when running from /etc/rc.c/rc.local. Not applicable to the -i or -v or -t or -T flags. -r Get/set read-only flag for device. When set, write operations are not permitted on the device. -R Register an IDE interface. Dangerous. See the -U option for more information. -S Set the standby (spindown) timeout for the drive. This value is used by the drive to determine how long to wait (with no disk activity) before turning off the spindle motor to save power. Under such circumstances, the drive may take as long as 30 seconds to respond to a subsequent disk access, though most drives are much quicker. The encoding of the timeout value is somewhat peculiar. A value of zero means "off". Values from 1 to 240 specify multiples of 5 seconds, for timeouts from 5 seconds to 20 minutes. Values from 241 to 251 specify from 1 to 11 units of 30 minutes, for timeouts from 30 minutes to 5.5 hours. A value of 252 signifies a timeout of 21 minutes, 253 sets a vendor-defined timeout, and 255 is interpreted as 21 minutes plus 15 seconds. -T Perform timings of cache reads for benchmark and comparison purposes. For meaningful results, this operation should be repeated 2-3 times on an otherwise inactive system (no other active pro? cesses) with at least a couple of megabytes of free memory. This displays the speed of reading directly from the Linux buffer cache without disk access. This measurement is essentially an indication of the throughput of the processor, cache, and memory of the system under test. If the -t flag is also specified, then a correction factor based on the outcome of -T will be incor? porated into the result reported for the -t operation. -t Perform timings of device reads for benchmark and comparison purposes. For meaningful results, this operation should be repeated 2-3 times on an otherwise inactive system (no other active pro? cesses) with at least a couple of megabytes of free memory. This displays the speed of reading through the buffer cache to the disk without any prior caching of data. This measurement is an indication of how fast the drive can sustain sequential data reads under Linux, without any filesystem overhead. To ensure accurate measurments, the buffer cache is flushed during the pro? cessing of -t using the BLKFLSBUF ioctl. If the -T flag is also specified, then a correction factor based on the outcome of -T will be incorporated into the result reported for the -t opera? tion. -u Get/set interrupt-unmask flag for the drive. A setting of 1 permits the driver to unmask other interrupts during processing of a disk interrupt, which greatly improves Linuxs responsiveness and eliminates "serial port overrun" errors. Use this feature with caution: some drive/con? troller combinations do not tolerate the increased I/O latencies possible when this feature is enabled, resulting in massive filesystem corruption. In particular, CMD-640B and RZ1000 (E)IDE interfaces can be unreliable (due to a hardware flaw) when this option is used with kernel ver? sions earlier than -U Un-register an IDE interface. Dangerous. The companion for the -R option. Intended for use with hardware made specifically for hot-swapping (very rare!). Use with knowledge and extreme caution as this can easily hang or damage your system. The hdparm source distribution includes a contrib directory with some user-donated scripts for hot-swapping on the UltraBay of a ThinkPad 600E. Use at your own risk. -v Display all settings, except -i (same as -acdgkmnru for IDE, -gr for SCSI or -adgr for XT). This is also the default behaviour when no flags are specified. -W Disable/enable the IDE drives write-caching feature (usually OFF by default). -X Set the IDE transfer mode for newer (E)IDE/ATA2 drives. This is typically used in combination with -d1 when enabling DMA to/from a drive on a supported interface chipset (such as the Intel 430FX Triton), where -X34 is used to select multiword DMA mode2 transfers. With systems which support UltraDMA burst timings, -X66 is used to select UltraDMA mode2 transfers (youll need to prepare the chipset for UltraDMA beforehand). Apart from that, use of this flag is seldom neces? sary since most/all modern IDE drives default to their fastest PIO transfer mode at power-on. Fiddling with this can be both needless and risky. On drives which support alternate transfer modes, -X can be used to switch the mode of the drive only. Prior to changing the transfer mode, the IDE interface should be jumpered or programmed (see -p flag) for the new mode setting to pre? vent loss and/or corruption of data. Use this with extreme caution! For the PIO (Programmed Input/Output) transfer modes used by Linux, this value is simply the desired PIO mode number plus 8. Thus, a value of 09 sets PIO mode1, 10 enables PIO mode2, and 11 selects PIO mode3. Setting 00 restores the drives "default" PIO mode, and 01 disables IORDY. For multiword DMA, the value used is the desired DMA mode number plus 32. for UltraDMA, the value is the desired UltraDMA mode number plus 64. -y Force an IDE drive to immediately enter the low power consumption standby mode, usually causing it to spin down. The current power mode status can be checked using the -C flag. -Y Force an IDE drive to immediately enter the lowest power consumption sleep mode, causing it to shut down completely. A hard or soft reset is required before the drive can be accessed again (the Linux IDE driver will automatically handle issuing a reset if/when needed). The current power mode status can be checked using the -C flag. -Z Disable the automatic power-saving function of certain Seagate drives (ST3xxx models?), to pre? vent them from idling/spinning-down at inconvenient times. BUGS As noted above, the -m sectcount and -u 1 options should be used with caution at first, preferably on a read-only filesystem. Most drives work well with these features, but a few drive/controller combina? tions are not 100% compatible. Filesystem corruption may result. Backup everything before experiment? ing! Some options (eg. -r for SCSI) may not work with old kernels as necessary ioctl()s were not supported. Although this utility is intended primarily for use with (E)IDE hard disk devices, several of the options are also valid (and permitted) for use with SCSI hard disk devices and MFM/RLL hard disks with XT interfaces. AUTHOR hdparm has been written by Mark Lord <mlord@pobox.com>, the primary developer and maintainer of the (E)IDE driver for Linux, with suggestions from many netfolk. The disable Seagate auto-powersaving code is courtesy of Tomi Leppikangas(tomilepp@paju.oulu.fi). SEE ALSO AT Attachment Interface for Disk Drives, ANSI ASC X3T9.2 working draft, revision AT Attachment Interface with Extensions (ATA-2), ANSI ASC X3T9.2 working draft, revision Western Digital Enhanced IDE Implementation Guide, by Western Digital Corporation, revision 5.0, Novem? ber 10, 1993. Enhanced Disk Drive Specification, by Phoenix Technologies Ltd., version 1.0, January 25, 1994. Version 3.9 February 2000 1 [Category:Linux]] 4, Speeding up Linux Using hdparmhttp://www./article/server/00070002/0621409064857145.htm Are you running an Intel Linux system with at least one (E)IDE hard drive?
Wouldn‘t it be neat if there were a magical command to instantly double the I/O performance of your disks? Or, in some cases, show 6 to 10 times your existing throughput? Did you ever just wonder how to tell what kind of performance you‘re getting on your "tricked-out" Linux box? Don‘t overlook hdparm(. If you‘ve never heard of it, don‘t worry. Most people I‘ve talked to haven‘t either. But if you‘re running an IDE/Linux system (as many folks are,) you‘ll wonder how you ever got this far without it. I know I did. What‘s the big deal? So, you‘ve got your brand-new UltraATA/66 EIDE drive with a screaming brand-new controller chipset that supports multiple PIO modes and DMA and the leather seat option and extra chrome... But is your system actually taking advantage of these snazzy features? The hdparm( command will not only tell you how your drives are performing, but will let you tweak them out to your heart‘s content. Now before you get too excited, it is worth pointing out that under some circumstances, these commands CAN CAUSE UNEXPECTED DATA CORRUPTION! Use them at your own risk! At the very least, back up your box and bring it down to single-user mode before proceeding. With the usual disclaimer out of the way, I‘d like to point out that if you are using current hardware (i.e. your drive AND controller AND motherboard were manufactured in the last two or three years), you are at considerably lower risk. I‘ve used these commands on several boxes with various hardware configurations, and the worst I‘ve seen happen is the occasional hang, with no data problems on reboot. And no matter how much you might whine at me and the world in general for your personal misfortune, we all know who is ultimately responsible for the well-being of YOUR box: YOU ARE. Caveat Fair Reader. Now, then. If I haven‘t scared you away yet, try this (as root, preferably in single-user mode): hdparm -Tt /dev/hda You‘ll see something like: /dev/hda: Timing buffer-cache reads: 128 MB in 1.34 seconds =95.52 MB/sec Timing buffered disk reads: 64 MB in 17.86 seconds = 3.58 MB/sec What does this tell us? The -T means to test the cache system (i.e., the memory, CPU, and buffer cache). The -t means to report stats on the disk in question, reading data not in the cache. The two together, run a couple of times in a row in single-user mode, will give you an idea of the performance of your disk I/O system. (These are actual numbers from a PII/350 / But even with varying numbers, 3.58 MB/sec is PATHETIC for the above hardware. I thought the ad for the HD said something about 66MB per second!!?!? What gives? Well, let‘s find out more about how Linux is addressing your drive: hdparm /dev/hda /dev/hda: multcount = 0 (off) I/O support = 0 (default 16-bit) unmaskirq = 0 (off) using_dma = 0 (off) keepsettings = 0 (off) nowerr = 0 (off) readonly = 0 (off) readahead = 8 (on) geometry = 1870/255/63, sectors = 30043440, start = 0 These are the defaults. Nice, safe, but not necessarily optimal. What‘s all this about 16-bit mode? I thought that went out with the 386! And why are most of the other options turned off? Well, it‘s generally considered a good idea for any self-respecting distribution to install itself in the kewlest, slickest, but SAFEST way it possibly can. The above settings are virtually guaranteed to work on any hardware you might throw at it. But since we know we‘re throwing something more than a dusty, 8-year-old, 16-bit multi-IO card at it, let‘s talk about the interesting options: 20.13 MB/sec. A far cry from the miniscule 3.58 we started with... By the way, notice how we specified the -m16 and -c3 switch again? That‘s because it doesn‘t remember your hdparm settings between reboots. Be sure to add the above line to your /etc/rc.d/* scripts once you‘re sure the system is stable (and preferably after your fsck runs; having an extensive fs check run with your controller in a flaky mode may be a good way to generate vast quantities of entropy, but it‘s no way to administer a system. At least not with a straight face...) Now, after running the benchmark a few more times, reboot in multi-user mode and fire up X. Load Netscape. And try not to fall out of your chair. In conclusion This is one of those interesting little tidbits that escapes many "seasoned" Linux veterans, especially since one never sees any indication that the system isn‘t using the most optimal settings. (Gee, all my kernel messages have looked fine....) And using hdparm isn‘t completely without risk, but is well worth investigating. And it doesn‘t stop at performance: hdparm lets you adjust various power saving modes as well. See the hdparm( for the final word. Many thanks to Mark Lord for putting together this nifty utility. If your particular distribution doesn‘t include hdparm (usually in /sbin or /usr/sbin), get it from the source at http://metalab./pub/Linux/system/hardware/ Happy hacking! |
|
|
