lkml.org 
[lkml]   [2004]   [Dec]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: 2.6.10-rc3: kswapd eats CPU on start of memory-eating task
    Nick Piggin wrote:
    > Andrew Morton wrote:
    >
    >> Voluspa <lista4@comhem.se> wrote:
    >>
    >>> Would be nice though if someone else could verify...
    >>
    >>
    >>
    >> Well I'd love to, but afaik the only workloads which we currently know of
    >> involve complex userspace apps which I have no experience running.
    >>
    >> Did anyone come up with a simple step-by-step procedure for
    >> reproducing the
    >> problem? It would be good if someone could do this, because I don't
    >> think
    >> we understand the root cause yet?
    >>
    >
    > I admit to generally being in the same boat as you with respect to
    > running complex userspace apps.
    >
    > However, based on this and other scattered reports, I'd say it seems
    > quite likely that token based thrashing control is the culprit. Based
    > on the cost/benefit, I wonder if we should disable TBTC by default for
    > 2.6.10, rather than trying to fix it, and try again for 2.6.11?
    >
    > Rik? Andrew?
    >
    > Also, it would be nice to have a sysctl to *completely* disable TBTC,
    > that would make testing easier.

    Logistically what makes sense is if a timeout of 0 is used as a test
    that completely disables it (avoids another sysctl too). In time for
    2.6.10 we should disable it by default until the regressions are better
    understood. Tuning it into a useful "on" position can happen later and I
    suspect requires more code.

    Con
    [unhandled content-type:application/pgp-signature]
    \
     
     \ /
      Last update: 2005-03-22 14:08    [W:4.560 / U:0.044 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site