linux-kernel - Should I choose SLOW

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

Date:	Sun, 05 Apr 2009 19:09:54 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	David Howells <dhowells@...hat.com>
CC:	LKML <linux-kernel@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Should I choose SLOW_WORK?

I am newly presented with


> Enable slow work thread pool (SLOW_WORK) [N/y/?] (NEW) ?
> 
> The slow work thread pool provides a number of dynamically allocated
> threads that can be used by the kernel to perform operations that
> take a relatively long time.
> 
> An example of this would be CacheFiles doing a path lookup followed
> by a series of mkdirs and a create call, all of which have to touch
> disk.


However, this does not tell me whether I need or want this.

And, why must the user make this choice at all?  Surely it can be 
auto-selected, if cachefs is enabled?  At a minimum, hide this under 
CONFIG_EMBEDDED or whatnot, so that most users don't see this choice, IMO.

	Jeff


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