linux-kernel - Re: [PATCH 1/2] mm/slob: Mark zone page state to get slab usage at /proc/meminfo

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]

Message-ID: <0000013a8ed646c2-4cc34bd5-19c3-4e99-9fa0-248cdbc24feb-000000@email.amazonses.com>
Date:	Tue, 23 Oct 2012 18:15:38 +0000
From:	Christoph Lameter <cl@...ux.com>
To:	Ezequiel Garcia <elezegarcia@...il.com>
cc:	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	Tim Bird <tim.bird@...sony.com>,
	Pekka Enberg <penberg@...nel.org>,
	Matt Mackall <mpm@...enic.com>
Subject: Re: [PATCH 1/2] mm/slob: Mark zone page state to get slab usage at
 /proc/meminfo

On Mon, 22 Oct 2012, Ezequiel Garcia wrote:

> SLUB handles large kmalloc allocations falling back
> to page-size allocations (kmalloc_large, etc).
> This path doesn't touch NR_SLAB_XXRECLAIMABLE zone item state.

Right. UNRECLAIMABLE allocations do not factor in reclaim decisions.

> Without fully understanding it, I've decided to implement the same
> behavior for SLOB,
> leaving page-size allocations unaccounted on /proc/meminfo.
>
> Is this expected / wanted ?

Yes that is fine.

> SLAB, on the other side, handles every allocation through some slab cache,
> so it always set the zone state.

Right but the caching barely has any effect at large sizes.

--
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/