linux-kernel - Re: [PATCH] ext4: slab caches set to SLAB_MEM

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: <2F5A5082-690F-4C74-A92F-6CC157489B46@mit.edu>
Date:	Sat, 19 Nov 2011 16:14:01 -0500
From:	Theodore Tso <tytso@....EDU>
To:	NamJae Jeon <linkinjeon@...il.com>
Cc:	Theodore Tso <tytso@....edu>, David Rientjes <rientjes@...gle.com>,
	linux-kernel@...r.kernel.org, linux-ext4@...r.kernel.org,
	Amit Sahrawat <amit.sahrawat83@...il.com>
Subject: Re: [PATCH] ext4: slab caches set to SLAB_MEM_SPREAD flags.

On Nov 19, 2011, at 10:40 AM, NamJae Jeon wrote:

> Thanks for your opinion.
> Have you thought that mem spread flags is not needed in group info
> caches same with page_io and mballoc ?

The group info structures are long lived structures that live a long time and will likely be accessed by many NUMA nodes.   So setting the men spread flag for the group info cache is more likely to be useful.   My guess is that any benefit will be extremely hard to measure (especially since the amount of memory used by the group info structures is a pittance compared to the memory used by the inode cache), but at least theoretically it would be sound to have that flag set with the group info slab cache.

Regards,

-- Ted

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