From: Andrew Morton <akpm@linux-foundation.org>
To: David Howells <dhowells@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
nfsv4@linux-nfs.org, viro@ZenIV.linux.org.uk
Subject: Re: [PATCH 01/45] Create a dynamically sized pool of threads for doing very slow work items [ver #41]
Date: Thu, 18 Dec 2008 23:15:11 -0800 [thread overview]
Message-ID: <20081218231511.d9201464.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081120144145.10667.39594.stgit@warthog.procyon.org.uk>
On Thu, 20 Nov 2008 14:41:45 +0000 David Howells <dhowells@redhat.com> wrote:
> Create a dynamically sized pool of threads for doing very slow work items, such
> as invoking mkdir() or rmdir() - things that may take a long time and may
> sleep, holding mutexes/semaphores and hogging a thread, and are thus unsuitable
> for workqueues.
>
> The number of threads is always at least a settable minimum, but more are
> started when there's more work to do, up to a limit. Because of the nature of
> the load, it's not suitable for a 1-thread-per-CPU type pool. A system with
> one CPU may well want several threads.
>
> This is used by FS-Cache to do slow caching operations in the background, such
> as looking up, creating or deleting cache objects.
>
This may be the most skilfully commented kernel code I've ever seen.
>
> ...
>
> +/*
> + * The pool of threads has at least min threads in it as long as someone is
> + * using the facility, and may have as many as max.
> + *
> + * A portion of the pool may be processing very slow operations.
> + */
> +static unsigned slow_work_min_threads = 2;
> +static unsigned slow_work_max_threads = (NR_CPUS > 4) ? NR_CPUS : 4;
I suspect there will be a requirement to tune this at runtime.
Using num_possible_cpus() would be more accurate here. One could
easily envisage NR_CPUS=1024 on a 2-way machine. Generally any use
of NR_CPUS is a red flag. In fact there's a checkpatch warning about
it now.
>
> ...
>
> +static int slow_work_thread(void *_data)
> +{
> + int vsmax;
> +
> + DEFINE_WAIT(wait);
> +
> +#define slow_work_available(vsmax) \
> + (!list_empty(&slow_work_queue) || \
> + (!list_empty(&vslow_work_queue) && \
> + atomic_read(&vslow_work_executing_count) < (vsmax)))
This could be a regular C function?
> + set_freezable();
> + set_user_nice(current, -5);
> +
> + for (;;) {
> + vsmax = vslow_work_proportion;
> + vsmax *= atomic_read(&slow_work_thread_count);
> + vsmax /= 100;
> +
> + prepare_to_wait(&slow_work_thread_wq, &wait,
> + TASK_INTERRUPTIBLE);
> + if (!freezing(current) &&
> + !slow_work_threads_should_exit &&
> + !slow_work_available(vsmax))
> + schedule();
> + finish_wait(&slow_work_thread_wq, &wait);
> +
> + try_to_freeze();
> +
> + vsmax = vslow_work_proportion;
> + vsmax *= atomic_read(&slow_work_thread_count);
> + vsmax /= 100;
> +
> + if (slow_work_available(vsmax) && slow_work_execute()) {
> + cond_resched();
> + continue;
> + }
> +
> + if (slow_work_threads_should_exit)
> + break;
> + }
> +
> + if (atomic_dec_and_test(&slow_work_thread_count))
> + complete_and_exit(&slow_work_last_thread_exited, 0);
> + return 0;
> +}
> +
>
> ...
>
> +int slow_work_register_user(void)
> +{
> + struct task_struct *p;
> + int loop;
> +
> + mutex_lock(&slow_work_user_lock);
> +
> + if (slow_work_user_count == 0) {
> + printk(KERN_NOTICE "Slow work thread pool: Starting up\n");
> + init_completion(&slow_work_last_thread_exited);
> +
> + slow_work_threads_should_exit = false;
> +
> + /* start the minimum number of threads */
> + for (loop = 0; loop < slow_work_min_threads; loop++) {
> + atomic_inc(&slow_work_thread_count);
> + p = kthread_create(slow_work_thread, NULL,
> + "kslow%Xd", loop);
> + if (!p)
> + goto error;
> + wake_up_process(p);
The above reimplements kthread_run().
> + }
> + printk(KERN_NOTICE "Slow work thread pool: Ready\n");
> + }
> +
> + slow_work_user_count++;
> + mutex_unlock(&slow_work_user_lock);
> + return 0;
> +
> +error:
> + if (atomic_dec_and_test(&slow_work_thread_count))
> + complete(&slow_work_last_thread_exited);
> + if (loop > 0) {
> + printk(KERN_ERR "Slow work thread pool:"
> + " Aborting startup on ENOMEM\n");
> + slow_work_threads_should_exit = true;
> + wake_up_all(&slow_work_thread_wq);
> + wait_for_completion(&slow_work_last_thread_exited);
> + printk(KERN_ERR "Slow work thread pool: Aborted\n");
> + }
> + mutex_unlock(&slow_work_user_lock);
> + return PTR_ERR(p);
> +}
> +EXPORT_SYMBOL(slow_work_register_user);
next prev parent reply other threads:[~2008-12-19 7:15 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 14:41 [PATCH 00/45] Permit filesystem local caching [ver #41] David Howells
2008-11-20 14:41 ` [PATCH 01/45] Create a dynamically sized pool of threads for doing very slow work items " David Howells
2008-11-21 8:09 ` Andrew Morton
2008-11-21 10:24 ` David Howells
2008-11-21 18:17 ` Andrew Morton
2008-11-22 0:38 ` David Howells
2008-12-19 4:14 ` Serge E. Hallyn
2008-12-19 4:19 ` Serge E. Hallyn
2008-12-19 7:15 ` Andrew Morton [this message]
2008-12-19 11:42 ` David Howells
2008-12-19 11:44 ` David Howells
2008-12-19 12:12 ` David Howells
2008-12-19 16:52 ` Serge E. Hallyn
2008-12-19 12:54 ` David Howells
2008-11-20 14:41 ` [PATCH 02/45] Make slow-work thread pool actually dynamic " David Howells
2008-12-19 17:58 ` Serge E. Hallyn
2008-11-20 14:41 ` [PATCH 03/45] Make the slow work pool configurable " David Howells
2008-12-19 18:33 ` Serge E. Hallyn
2008-11-20 14:42 ` [PATCH 04/45] Document the slow work thread pool " David Howells
2008-11-20 14:42 ` [PATCH 05/45] FS-Cache: Release page->private after failed readahead " David Howells
2008-11-21 8:12 ` Andrew Morton
2008-11-21 10:27 ` David Howells
2008-11-20 14:42 ` [PATCH 06/45] FS-Cache: Recruit a couple of page flags for cache management " David Howells
2008-11-21 8:17 ` Andrew Morton
2008-11-21 10:31 ` David Howells
2008-11-20 14:42 ` [PATCH 07/45] FS-Cache: Provide an add_wait_queue_tail() function " David Howells
2008-11-21 8:17 ` Andrew Morton
2008-11-21 13:32 ` David Howells
2008-11-20 14:42 ` [PATCH 08/45] FS-Cache: Add the FS-Cache netfs API and documentation " David Howells
2008-11-20 14:42 ` [PATCH 09/45] FS-Cache: Add the FS-Cache cache backend " David Howells
2008-11-20 14:42 ` [PATCH 10/45] FS-Cache: Add main configuration option, module entry points and debugging " David Howells
2008-11-20 14:42 ` [PATCH 11/45] FS-Cache: Add use of /proc and presentation of statistics " David Howells
2008-11-21 0:15 ` Alexey Dobriyan
2008-11-21 2:17 ` David Howells
2008-11-21 2:34 ` Alexey Dobriyan
2008-11-21 15:32 ` David Howells
2008-11-20 14:42 ` [PATCH 12/45] FS-Cache: Root index definition " David Howells
2008-11-20 14:42 ` [PATCH 13/45] FS-Cache: Add cache tag handling " David Howells
2008-11-20 14:42 ` [PATCH 14/45] FS-Cache: Add cache management " David Howells
2008-11-20 14:42 ` [PATCH 15/45] FS-Cache: Provide a slab for cookie allocation " David Howells
2008-11-20 14:43 ` [PATCH 16/45] FS-Cache: Add netfs registration " David Howells
2008-11-20 14:43 ` [PATCH 17/45] FS-Cache: Bit waiting helpers " David Howells
2008-11-20 14:43 ` [PATCH 18/45] FS-Cache: Object management state machine " David Howells
2008-11-20 14:43 ` [PATCH 19/45] FS-Cache: Implement the cookie management part of the netfs API " David Howells
2008-11-20 14:43 ` [PATCH 20/45] FS-Cache: Add and document asynchronous operation handling " David Howells
2008-11-20 14:43 ` [PATCH 21/45] FS-Cache: Implement data I/O part of netfs API " David Howells
2008-11-20 14:43 ` [PATCH 22/45] CacheFiles: Add missing copy_page export for ia64 " David Howells
2008-11-20 14:43 ` [PATCH 23/45] CacheFiles: Be consistent about the use of mapping vs file->f_mapping in Ext3 " David Howells
2008-11-22 17:38 ` Andreas Dilger
2008-11-26 14:40 ` David Howells
2008-11-20 14:43 ` [PATCH 24/45] CacheFiles: Add a hook to write a single page of data to an inode " David Howells
2008-11-21 8:23 ` Andrew Morton
2008-11-21 12:43 ` David Howells
2008-11-21 13:00 ` Jamie Lokier
2008-11-21 17:15 ` Valdis.Kletnieks
2008-11-21 17:36 ` Randy Dunlap
2008-11-21 18:31 ` Andrew Morton
2008-11-22 0:48 ` David Howells
2008-11-20 14:43 ` [PATCH 25/45] CacheFiles: Permit the page lock state to be monitored " David Howells
2008-11-20 14:43 ` [PATCH 26/45] CacheFiles: Export things for CacheFiles " David Howells
2008-11-20 14:43 ` [PATCH 27/45] CacheFiles: A cache that backs onto a mounted filesystem " David Howells
2008-11-20 14:44 ` [PATCH 28/45] FS-Cache: Make kAFS use FS-Cache " David Howells
2008-11-20 14:44 ` [PATCH 29/45] NFS: Add comment banners to some NFS functions " David Howells
2008-11-20 14:44 ` [PATCH 30/45] NFS: Add FS-Cache option bit and debug bit " David Howells
2008-11-20 14:44 ` [PATCH 31/45] NFS: Permit local filesystem caching to be enabled for NFS " David Howells
2008-11-20 14:44 ` [PATCH 32/45] NFS: Register NFS for caching and retrieve the top-level index " David Howells
2008-11-20 14:44 ` [PATCH 33/45] NFS: Define and create server-level objects " David Howells
2008-11-20 14:44 ` [PATCH 34/45] NFS: Define and create superblock-level " David Howells
2008-11-20 14:44 ` [PATCH 35/45] NFS: Define and create inode-level cache " David Howells
2008-11-20 14:44 ` [PATCH 36/45] NFS: Use local disk inode cache " David Howells
2008-11-20 14:44 ` [PATCH 37/45] NFS: Invalidate FsCache page flags when cache removed " David Howells
2008-11-20 14:44 ` [PATCH 38/45] NFS: Add some new I/O counters for FS-Cache doing things for NFS " David Howells
2008-11-20 14:45 ` [PATCH 39/45] NFS: FS-Cache page management " David Howells
2008-11-20 14:45 ` [PATCH 40/45] NFS: Add read context retention for FS-Cache to call back with " David Howells
2008-11-20 14:45 ` [PATCH 41/45] NFS: nfs_readpage_async() needs to be accessible as a fallback for local caching " David Howells
2008-11-20 14:45 ` [PATCH 42/45] NFS: Read pages from FS-Cache into an NFS inode " David Howells
2008-11-20 14:45 ` [PATCH 43/45] NFS: Store pages from an NFS inode into a local cache " David Howells
2008-11-20 14:45 ` [PATCH 44/45] NFS: Display local caching state " David Howells
2008-11-20 14:45 ` [PATCH 45/45] NFS: Add mount options to enable local caching on NFS " David Howells
2008-11-21 8:28 ` [PATCH 00/45] Permit filesystem local caching " Andrew Morton
2008-11-22 1:11 ` David Howells
2008-11-25 0:09 ` David Howells
2008-11-25 13:39 ` FS-Cache Benchmarks David Howells
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=20081218231511.d9201464.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=viro@ZenIV.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).