linux-kernel - Re: [PATCH 1/1] Security : smack : Use kmem_cache for allocation and freeing of inode

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

Message-Id: <20141014224338.f58a66e5.akpm@linux-foundation.org>
Date:	Tue, 14 Oct 2014 22:43:38 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Rohit Kumar <rohit.kr@...sung.com>
Cc:	casey@...aufler-ca.com, james.l.morris@...cle.com,
	serge@...lyn.com, linux-security-module@...r.kernel.org,
	linux-kernel@...r.kernel.org, cpgs@...sung.com,
	pintu.k@...sung.com, vishnu.ps@...sung.com, iqbal.ams@...sung.com,
	ed.savinay@...sung.com
Subject: Re: [PATCH 1/1] Security : smack : Use kmem_cache for allocation
 and freeing of inode_smack

On Wed, 15 Oct 2014 11:26:16 +0530 Rohit Kumar <rohit.kr@...sung.com> wrote:

> From: Rohit <rohit.kr@...sung.com>
> 
> Use kmem_cache to allocate/free inode_smack since they are
> alloced in high volumes making it a perfect case for kmem_cache.
> 
> Accounting of memory allocation is below :
>  total           slack            net      count-alloc/free        caller
> Before (with kzalloc)
> 1919872           719952          1919872      29998/0          new_inode_smack+0x14
> After (with kmem_cache)
> 1201680                0          1201680      30042/0          new_inode_smack+0x18
> 
> ...
>
> --- a/security/smack/smack_lsm.c
> +++ b/security/smack/smack_lsm.c
> @@ -53,6 +53,7 @@
>  #define SMK_SENDING	2
>  
>  LIST_HEAD(smk_ipv6_port_list);
> +struct kmem_cache *smack_inode_cache;

static.
  

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