From: Jeff Garzik <jeff@garzik.org>
To: David Howells <dhowells@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Should I choose SLOW_WORK?
Date: Sun, 05 Apr 2009 19:09:54 -0400 [thread overview]
Message-ID: <49D93A42.2030009@garzik.org> (raw)
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
next reply other threads:[~2009-04-05 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 23:09 Jeff Garzik [this message]
2009-04-05 23:33 ` Jesper Juhl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49D93A42.2030009@garzik.org \
--to=jeff@garzik.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®