lkml.org 
[lkml]   [2001]   [Jun]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: 2.4.6-pre2, pre3 VM Behavior

    >> The file _could_ be a temporary file, which gets removed before
    >> we'd get around to writing it to disk. Sure, the chances of this
    >> happening with a single file are close to zero, but having 100MB
    >> from 200 different temp files on a shell server isn't unreasonable
    >> to expect.

    Daniel> This still doesn't make sense if the disk bandwidth isn't
    Daniel> being used.

    And can't you tell that a certain percentage of buffers are owned by a
    single file/process? It would seem that a simple metric of

    if ##% of the buffer/cache is used by 1 process/file, start
    writing the file out to disk, even if there is no pressure.

    might to the trick to handle this case.

    >> Maybe we should just see if anything in the first few MB of
    >> inactive pages was freeable, limiting the first scan to something
    >> like 1 or maybe even 5 MB maximum (freepages.min? freepages.high?)
    >> and flushing as soon as we find more unfreeable pages than that ?

    Daniel> For file-backed pages what we want is pretty simple: when 1)
    Daniel> disk bandwidth is less than xx% used 2) memory pressure is
    Daniel> moderate, just submit whatever's dirty. As pressure increases
    Daniel> and bandwidth gets loaded up (including read traffic) leave
    Daniel> things on the inactive list longer to allow more chances for
    Daniel> combining and better clustering decisions.

    Would it also be good to say that pressure should increase as the
    buffer.free percentage goes down? It won't stop you from filling the
    buffer, but it should at least start pushing out pages to disk
    earlier.

    John
    John Stoffel - Senior Unix Systems Administrator - Lucent Technologies
    stoffel@lucent.com - http://www.lucent.com - 978-952-7548
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 12:55    [W:0.021 / U:0.364 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site