From: Jan Kara <jack@suse.cz>
To: Jeff Layton <jlayton@poochiereds.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Jan Kara <jack@suse.com>, Eric Paris <eparis@parisplace.org>,
Eryu Guan <guaneryu@gmail.com>
Subject: Re: [PATCH 2/2] fsnotify: turn fsnotify reaper thread into a workqueue job
Date: Wed, 17 Feb 2016 21:01:36 +0100 [thread overview]
Message-ID: <20160217200136.GB14140@quack.suse.cz> (raw)
In-Reply-To: <1455495323-29605-2-git-send-email-jeff.layton@primarydata.com>
On Sun 14-02-16 19:15:23, Jeff Layton wrote:
> We don't require a dedicated thread for fsnotify cleanup. Switch it over
> to a workqueue job instead that runs on the system_unbound_wq.
>
> In the interest of not thrashing the queued job too often when there are
> a lot of marks being removed, we delay the reaper job slightly when
> queueing it, to allow several to gather on the list.
>
> Cc: Jan Kara <jack@suse.com>
> Cc: Eric Paris <eparis@parisplace.org>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Eryu Guan <guaneryu@gmail.com>
> Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
The patch looks correct to me. You can add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> fs/notify/mark.c | 49 ++++++++++++++++++-------------------------------
> 1 file changed, 18 insertions(+), 31 deletions(-)
>
> diff --git a/fs/notify/mark.c b/fs/notify/mark.c
> index fc0df4442f7b..7115c5d7d373 100644
> --- a/fs/notify/mark.c
> +++ b/fs/notify/mark.c
> @@ -91,10 +91,14 @@
> #include <linux/fsnotify_backend.h>
> #include "fsnotify.h"
>
> +#define FSNOTIFY_REAPER_DELAY (1) /* 1 jiffy */
> +
> struct srcu_struct fsnotify_mark_srcu;
> static DEFINE_SPINLOCK(destroy_lock);
> static LIST_HEAD(destroy_list);
> -static DECLARE_WAIT_QUEUE_HEAD(destroy_waitq);
> +
> +static void fsnotify_mark_destroy(struct work_struct *work);
> +static DECLARE_DELAYED_WORK(reaper_work, fsnotify_mark_destroy);
>
> void fsnotify_get_mark(struct fsnotify_mark *mark)
> {
> @@ -189,7 +193,8 @@ void fsnotify_free_mark(struct fsnotify_mark *mark)
> spin_lock(&destroy_lock);
> list_add(&mark->g_list, &destroy_list);
> spin_unlock(&destroy_lock);
> - wake_up(&destroy_waitq);
> + queue_delayed_work(system_unbound_wq, &reaper_work,
> + FSNOTIFY_REAPER_DELAY);
>
> /*
> * Some groups like to know that marks are being freed. This is a
> @@ -388,7 +393,8 @@ err:
> spin_lock(&destroy_lock);
> list_add(&mark->g_list, &destroy_list);
> spin_unlock(&destroy_lock);
> - wake_up(&destroy_waitq);
> + queue_delayed_work(system_unbound_wq, &reaper_work,
> + FSNOTIFY_REAPER_DELAY);
>
> return ret;
> }
> @@ -493,39 +499,20 @@ void fsnotify_init_mark(struct fsnotify_mark *mark,
> mark->free_mark = free_mark;
> }
>
> -static int fsnotify_mark_destroy(void *ignored)
> +static void fsnotify_mark_destroy(struct work_struct *work)
> {
> struct fsnotify_mark *mark, *next;
> struct list_head private_destroy_list;
>
> - for (;;) {
> - spin_lock(&destroy_lock);
> - /* exchange the list head */
> - list_replace_init(&destroy_list, &private_destroy_list);
> - spin_unlock(&destroy_lock);
> -
> - synchronize_srcu(&fsnotify_mark_srcu);
> + spin_lock(&destroy_lock);
> + /* exchange the list head */
> + list_replace_init(&destroy_list, &private_destroy_list);
> + spin_unlock(&destroy_lock);
>
> - list_for_each_entry_safe(mark, next, &private_destroy_list, g_list) {
> - list_del_init(&mark->g_list);
> - fsnotify_put_mark(mark);
> - }
> + synchronize_srcu(&fsnotify_mark_srcu);
>
> - wait_event_interruptible(destroy_waitq, !list_empty(&destroy_list));
> + list_for_each_entry_safe(mark, next, &private_destroy_list, g_list) {
> + list_del_init(&mark->g_list);
> + fsnotify_put_mark(mark);
> }
> -
> - return 0;
> -}
> -
> -static int __init fsnotify_mark_init(void)
> -{
> - struct task_struct *thread;
> -
> - thread = kthread_run(fsnotify_mark_destroy, NULL,
> - "fsnotify_mark");
> - if (IS_ERR(thread))
> - panic("unable to start fsnotify mark destruction thread.");
> -
> - return 0;
> }
> -device_initcall(fsnotify_mark_init);
> --
> 2.5.0
>
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2016-02-17 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 0:15 [PATCH 1/2] Revert "fsnotify: destroy marks with call_srcu instead of dedicated thread" Jeff Layton
2016-02-15 0:15 ` [PATCH 2/2] fsnotify: turn fsnotify reaper thread into a workqueue job Jeff Layton
2016-02-15 6:03 ` Eryu Guan
2016-02-15 17:55 ` Jeff Layton
2016-02-17 20:01 ` Jan Kara [this message]
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=20160217200136.GB14140@quack.suse.cz \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=eparis@parisplace.org \
--cc=guaneryu@gmail.com \
--cc=jack@suse.com \
--cc=jlayton@poochiereds.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
/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).