DragonFly BSD
DragonFly bugs List (threaded) for 2010-03
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

[no subject]


apollo.backplane.com> <20100323090705.GA1138@sekishi.zefyris.com>
From: Matthew Dillon <dillon@apollo.backplane.com>
Subject: Re: Machine unresponsive with cache_lock: blocked on... message
Date: Tue, 23 Mar 2010 09:11:40 -0700 (PDT)
BestServHost: crater.dragonflybsd.org
List-Post: <mailto:bugs@crater.dragonflybsd.org>
List-Subscribe: <mailto:bugs-request@crater.dragonflybsd.org?body=subscribe>
List-Unsubscribe: <mailto:bugs-request@crater.dragonflybsd.org?body=unsubscribe>
List-Help: <mailto:bugs-request@crater.dragonflybsd.org?body=help>
List-Owner: <mailto:owner-bugs@crater.dragonflybsd.org>
Sender: bugs-errors@crater.dragonflybsd.org
Errors-To: bugs-errors@crater.dragonflybsd.org
Lines: 29
X-Trace: 1269360809 crater_reader.dragonflybsd.org 55375
Xref: crater_reader.dragonflybsd.org dragonfly.bugs:11565

:I'm not completely happy either: even with 40 some applications get paged out,
:which didn't occur with 2.4.

    There's nothing wrong with an application getting paged out if it
    is idle.  It really isn't a bad thing.  It frees up memory for the
    apps which ARE running.

    What people don't seem to like is when a lot of apps get paged out
    overnight in order to satisfy certain overnight operations which
    operate on a very large data set (the entire filesystem) and
    can't be cached anyway.

:I also had a new deadlock this night (possibly during the daily periodic run).
:Symptoms were the same as usual: no keyboard input, no network activity, many
:pmap_interlock messages on the console...
:The new crash dump is there: http://www.wolfpond.org/crash.dfly/
:I have now set vfs.vm_cycle_point to 64 just in case. I may still be
:positively surprised...
:Francois Tigeot

    Ok, I'll look at it.

					Matthew Dillon 

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]