linux-kernel - Re: VM - a plenty of inactive memory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-id: <47FCD37B.3040103@shaw.ca>
Date:	Wed, 09 Apr 2008 08:32:27 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	Andreas Grimm <agrimm61@...il.com>
Cc:	Johannes Weiner <hannes@...urebad.de>, linux-kernel@...r.kernel.org
Subject: Re: VM - a plenty of inactive memory

Andreas Grimm wrote:
> Hi Johannes,
> 
> i know this. But why the kernel locks that memory for a so long time
> (2 days now)? Is there a way to enforce the reclaiming? And how can i
> find out, which process owns that memory. The problem is, that i can't
> accept, that the free memory fell down to 50MB, when i have 24GB in
> the nirvana. The system was recently very close to the awkward
> situation to swap to disk, and i bet it will do so in the next few
> days, because it happened before. Unintelligible, if one got that much
> ram.
> 
> Bye, Andreas

The memory should not be locked. If the kernel has no reason to reclaim 
the memory, it won't, though.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/