lkml.org 
[lkml]   [2004]   [Apr]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: ~500 megs cached yet 2.6.5 goes into swap hell
    Andrew wrote:
    > Even if the background activity was clamped to just a few megs
    > of cache you'll find that the seek activity is a killer, and
    > needs a limitation mechanism.

    True - the seek activity is another critical resource that would need to
    be throttled to keep updatedb/backup from interferring with my late
    night labours.

    Let's see, that's:
    1) cpu scheduling ticks
    2) memory for virtual address backing store
    3) memory for file related caching
    4) disk arm motion

    Hmmm ... actually not so much a numa-placement extension, but rather a
    CKRM opportunity.

    CKRM focuses on measuring and restraining how much of specified critical
    resources a task is using; numa placement on which cpus or memory nodes
    are allowed to be used at all.

    See further the CKRM thread of Shailabh Nagar, also running on lkml
    today.

    --
    I won't rest till it's the best ...
    Programmer, Linux Scalability
    Paul Jackson <pj@sgi.com> 1.650.933.1373
    -
    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 14:02    [W:0.027 / U:31.388 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site