From: Oleg Nesterov <oleg@tv-sign.ru>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jarek Poplawski <jarkao2@o2.pl>,
Max Krasnyansky <maxk@qualcomm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] workqueues: insert_work: use "list_head *" instead of "int tail"
Date: Thu, 12 Jun 2008 21:44:33 +0400 [thread overview]
Message-ID: <20080612174433.GA12204@tv-sign.ru> (raw)
In-Reply-To: <1213290074.31518.136.camel@twins>
On 06/12, Peter Zijlstra wrote:
>
> On Thu, 2008-06-12 at 20:55 +0400, Oleg Nesterov wrote:
> >
> > This allows us to implement
> >
> > int flush_work(struct work_struct *work)
> > {
> > struct cpu_workqueue_struct *cwq;
> > struct list_head *head;
> > struct wq_barrier barr;
> >
> > cwq = get_wq_data(work);
> > if (!cwq)
> > return 0;
> >
> > head = NULL;
> > spin_lock_irq(&cwq->lock);
> > if (!list_empty(&work->entry)) {
> > smp_rmb();
> > /*
> > * ---- FAT COMMENT ----
> > */
> > if (cwq == get_wq_data(work))
> > head = work->entry.next;
> > } else if (cwq->current_work == work) {
> > head = cwq->worklist.next;
> > }
> >
> > if (head)
> > insert_wq_barrier(cwq, &barr, head);
> > spin_unlock_irq(&cwq->lock);
> >
> > if (!head)
> > return 0;
> > wait_for_completion(&barr.done);
> > return 1;
> > }
> >
> > suggested by Peter. It only waits for selected work_struct.
> >
> > I doubt it will have a lot of users though. In most cases we need
> > cancel_work_sync() and nothing more.
>
> Are there cases where we dynamically allocate work structs and queue
> them and then forget about them? In such cases we'd need something a
> little more complex as we don't have work pointers to flush or cancel.
>
> Hence that idea of flush context and completions.
Do you mean something like (just for example) below? If yes, then yes
sure, flush_work() is limited. But I can't see how it is possible to
"generalize" this idea.
(hmm... actually, if we add flush_work(), we can speedup schedule_on_each_cpu(),
instead of flush_workqueue(keventd_wq) we can do
for_each_online_cpu(cpu)
flush_work(per_cpu_ptr(works, cpu));
not sure this really makes sense though).
Oleg.
--- kernel/workqueue.c~ 2007-07-28 16:58:17.000000000 +0400
+++ kernel/workqueue.c 2007-08-06 20:33:25.000000000 +0400
@@ -590,25 +590,54 @@ EXPORT_SYMBOL(schedule_delayed_work_on);
*
* schedule_on_each_cpu() is very slow.
*/
+
+struct xxx
+{
+ atomic_t count;
+ struct completion done;
+ work_func_t func;
+};
+
+struct yyy
+{
+ struct work_struct work;
+ struct xxx *xxx;
+};
+
+static void yyy_func(struct work_struct *work)
+{
+ struct xxx *xxx = container_of(work, struct yyy, work)->xxx;
+ xxx->func(work);
+
+ if (atomic_dec_and_test(&xxx->count))
+ complete(&xxx->done);
+}
+
int schedule_on_each_cpu(work_func_t func)
{
int cpu;
- struct work_struct *works;
+ struct xxx xxx;
+ struct yyy *works;
- works = alloc_percpu(struct work_struct);
+ init_completion(&xxx.done);
+ xxx.func = func;
+
+ works = alloc_percpu(struct yyy);
if (!works)
return -ENOMEM;
get_online_cpus();
+ atomic_set(&xxx.count, num_online_cpus());
for_each_online_cpu(cpu) {
- struct work_struct *work = per_cpu_ptr(works, cpu);
+ struct yyy *yyy = per_cpu_ptr(works, cpu);
- INIT_WORK(work, func);
- set_bit(WORK_STRUCT_PENDING, work_data_bits(work));
- __queue_work(per_cpu_ptr(keventd_wq->cpu_wq, cpu), work);
+ yyy->xxx = &xxx;
+ INIT_WORK(&yyy->work, yyy_func);
+ set_bit(WORK_STRUCT_PENDING, work_data_bits(&yyy->work));
+ __queue_work(per_cpu_ptr(keventd_wq->cpu_wq, cpu), &yyy->work);
}
- flush_workqueue(keventd_wq);
put_online_cpus();
+ wait_for_completion(&xxx.done);
free_percpu(works);
return 0;
}
next prev parent reply other threads:[~2008-06-12 17:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 16:51 Oleg Nesterov
2008-06-12 16:55 ` Oleg Nesterov
2008-06-12 17:01 ` Peter Zijlstra
2008-06-12 17:44 ` Oleg Nesterov [this message]
2008-06-12 18:38 ` Peter Zijlstra
2008-06-13 14:26 ` Oleg Nesterov
2008-06-13 14:43 ` Peter Zijlstra
2008-06-13 15:17 ` Oleg Nesterov
2008-06-13 15:32 ` Peter Zijlstra
2008-06-24 5:41 ` Max Krasnyansky
2008-06-12 22:24 ` Jarek Poplawski
2008-06-13 10:13 ` Jarek Poplawski
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=20080612174433.GA12204@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akpm@linux-foundation.org \
--cc=jarkao2@o2.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--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
all inboxes | Powered by JetHome®