[lkml]   [2001]   [Nov]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Unresponiveness of 2.4.16
    At 10:17 PM 26/11/2001 +0000, Alan Cox wrote:
    > > 2.4.16 becomes very unresponsive for 30 seconds or so at a time during
    > > large unarchiving of tarballs, like tar -zxf mozilla-src.tar.gz. The
    > > file is about 36mb. I run top in one window, run free repeatedly in
    >This seems to be one of the small as yet unresolved problems with the newer
    >VM code in 2.4.16. I've not managed to prove its the VM or the differing
    >I/O scheduling rules however.

    it is I/O scheduling.

    i have a system with a large amount of RAM.
    it has both 15K RPM SCSI disks (off a symbios controller) and some bog-slow
    IDE/ATA disks which the system decides to use PIO for rather than DMA. (i
    don't use them for anything other than bootup so don't really care about it
    deciding to use PIO..).

    a copy to/from the 15K RPM SCSI disks doesn't show any performance problems.
    a copy to/from the PIO-based IDE disks has the same effect -- 20/30 seconds
    of no interactiveness -- even a "vmstat 1" *stops* for 20-30 seconds while
    200+MB of buffer-cache data gets written out to disk.

    i'm guessing that:
    (a) the i/o scheduler isn't taking into account "disk speed" and thus
    slower disks
    show it more effectively than fast-disks
    (b) its isolated to somewhere in the IDE drivers



    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:13    [W:0.023 / U:79.348 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site