From: Jarek Poplawski <jarkao2@gmail.com>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jarek Poplawski <jarkao2@o2.pl>,
Max Krasnyansky <maxk@qualcomm.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] workqueues: implement flush_work()
Date: Mon, 30 Jun 2008 15:25:12 +0200 [thread overview]
Message-ID: <20080630132512.GA2663@ami.dom.local> (raw)
In-Reply-To: <20080629144926.GA4347@tv-sign.ru>
On Sun, Jun 29, 2008 at 06:49:26PM +0400, Oleg Nesterov wrote:
...
> --- 26-rc2/kernel/workqueue.c~WQ_2_FLUSH_WORK 2008-06-12 21:28:13.000000000 +0400
> +++ 26-rc2/kernel/workqueue.c 2008-06-29 18:20:33.000000000 +0400
> @@ -399,6 +399,52 @@ void flush_workqueue(struct workqueue_st
> }
> EXPORT_SYMBOL_GPL(flush_workqueue);
>
> +/**
> + * flush_work - block until a work_struct's callback has terminated
> + * @work: the work which is to be flushed
> + *
> + * It is expected that, prior to calling flush_work(), the caller has
> + * arranged for the work to not be requeued, otherwise it doesn't make
> + * sense to use this function.
> + */
I missed this before, and probably it's not required, but "Returns..."
could be added here.
> +int flush_work(struct work_struct *work)
> +{
> + struct cpu_workqueue_struct *cwq;
> + struct list_head *prev;
> + struct wq_barrier barr;
> +
> + might_sleep();
> + cwq = get_wq_data(work);
> + if (!cwq)
> + return 0;
> +
> + prev = NULL;
> + spin_lock_irq(&cwq->lock);
> + if (!list_empty(&work->entry)) {
> + /*
> + * See the comment near try_to_grab_pending()->smp_rmb().
> + * If it was re-queued under us we are not going to wait.
> + */
> + smp_rmb();
> + if (unlikely(cwq != get_wq_data(work)))
> + goto out;
> + prev = &work->entry;
> + } else {
Probably it doesn't matter too much, but one little doubt: don't we
need (for consistency) smp_rmb() for this branch as well? It seems
this cwq could be read out of order here too.
> + if (cwq->current_work != work)
> + goto out;
> + prev = &cwq->worklist;
> + }
> + insert_wq_barrier(cwq, &barr, prev->next);
> +out:
> + spin_unlock_irq(&cwq->lock);
> + if (!prev)
> + return 0;
> +
> + wait_for_completion(&barr.done);
> + return 1;
> +}
> +EXPORT_SYMBOL_GPL(flush_work);
> +
> /*
> * Upon a successful return (>= 0), the caller "owns" WORK_STRUCT_PENDING bit,
> * so this work can't be re-armed in any way.
>
Otherwise, all looks correct to me as before.
Regards,
Jarek P.
next prev parent reply other threads:[~2008-06-30 13:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-29 14:49 [PATCH 2/3] workqueues: implement flush_work() Oleg Nesterov
2008-06-30 13:25 ` Jarek Poplawski [this message]
2008-07-01 12:50 ` Oleg Nesterov
2008-07-01 21:03 ` Jarek Poplawski
2008-07-02 16:33 ` Oleg Nesterov
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=20080630132512.GA2663@ami.dom.local \
--to=jarkao2@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jarkao2@o2.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=oleg@tv-sign.ru \
--cc=peterz@infradead.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