linux-ext4 - 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 19 Nov 2011 22:52:52 +0900
From:	NamJae Jeon <linkinjeon@...il.com>
To:	Theodore Tso <tytso@....edu>
Cc:	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.

2011/11/18 Theodore Tso <tytso@....edu>:
>
> On Nov 17, 2011, at 10:11 AM, Theodore Tso wrote:
>>
>> So accessing non-local memory can be a really, really big deal.  And this
>> isn't just theoretical, but have you considered what might happen on a 8
>> core AMD machine?
>
> Sorry, typo.  This should have read, "have you considered what might happen on a 8 _socket_ AMD machine"?
>
You're right. but..
It is only useful using cpuset, And have you read cpuset spread
history link of Amit provided ?
And why have you still used spread flags for inode cache ?
Thanks.

> -- Ted
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html