linux-kernel - Re: [PATCH 1/1] mmap: Don't count shmem pages as free in __vm_enough

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 4 Jul 2011 12:48:48 +0900
From:	Minchan Kim <minchan.kim@...il.com>
To:	"Dmitry Fink (Palm GBU)" <Dmitry.Fink@...m.com>
Cc:	Dmitry Fink <finikk@...il.com>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/1] mmap: Don't count shmem pages as free in __vm_enough_memory

On Mon, Jul 4, 2011 at 12:10 PM, Dmitry Fink (Palm GBU)
<Dmitry.Fink@...m.com> wrote:
> If I understand the logic correctly, even systems with swap set to
> OVERCOMMIT_GUESS are equally affected,
> what we are trying to do here is count the amount of immediately available
> and
> "potentially" available space both in memory and in swap. shmem is not
> immediately
> available, but it is not potentially available either, even if we swap it
> out, it will
> just be relocated from memory into swap, total amount of immediate and
> potentially
> available memory is not going to be affected, so we shouldn't count it as
> available
> in the first place.

Agree. I think this is good one rather than old description.

-- 
Kind regards,
Minchan Kim
--
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/