From: Jeff Garzik Subject: Should I choose SLOW_WORK? Date: Sun, 05 Apr 2009 19:09:54 -0400 Message-ID: <49D93A42.2030009@garzik.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: LKML , linux-fsdevel To: David Howells Return-path: Received: from srv5.dvmed.net ([207.36.208.214]:52099 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753466AbZDEXKA (ORCPT ); Sun, 5 Apr 2009 19:10:00 -0400 Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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