linux-kernel - Re: [PATCH] mm: move MACRO SLAB_NEVER_MERGE and SLAB_MERGE

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: <alpine.DEB.2.10.1501211443410.2716@chino.kir.corp.google.com>
Date:	Wed, 21 Jan 2015 14:44:49 -0800 (PST)
From:	David Rientjes <rientjes@...gle.com>
To:	Bryton Lee <brytonlee01@...il.com>
cc:	Christoph Lameter <cl@...ux.com>, iamjoonsoo.kim@....com,
	penberg@...nel.org, Andrew Morton <akpm@...ux-foundation.org>,
	linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm: move MACRO SLAB_NEVER_MERGE and SLAB_MERGE_SAME to
 file linux/slab.h

On Wed, 7 Jan 2015, Bryton Lee wrote:

> thanks for review my patch.
> 
> I want to move these macros to linux/slab.h cause I don't want perform
> merge in slab level.   for example. ss read /proc/slabinfo to finger out
> how many requests pending in the TCP listern queue.  it  use slabe name
> "tcp_timewait_sock_ops" search in /proc/slabinfo, although the name is
> obsolete. so I committed other patch  to iproute2, replaced
> tcp_timewait_sock_ops by request_sock_TCP, but it still not work, because
> slab request_sock_TCP  merge into kmalloc-256.
> 
> how could I prevent this merge happen.  I'm new to kernel, this is my first
> time submit a kernel patch, thanks!
> 

Any bit in SLAB_NEVER_MERGE will cause the allocator to not merge the slab 
caches, it's not necessary to all of them be set as it seems you're 
implying.
--
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/