From: Srivatsa Vaddagiri <vatsa@in.ibm.com>
To: mingo@redhat.com
Cc: rusty@au1.ibm.com, linux-kernel@vger.kernel.org
Subject: more efficient current_is_keventd macro? [was Re: [lhcs-devel] Re: Kthread_create() never returns when called from worker_thread]
Date: Mon, 8 Mar 2004 18:00:30 +0530 [thread overview]
Message-ID: <20040308123030.GA7428@in.ibm.com> (raw)
Hi Ingo,
current_is_keventd() macro checks "current" with the per-cpu
thread of _all_ possible cpus attached to keventd_wq. Can't it just check
against the per-cpu thread of _current_ cpu alone (since the per-cpu workqueue
threads are anyway bound only to their cpus)?
int current_is_keventd(void)
{
struct cpu_workqueue_struct *cwq;
- int cpu;
+ int cpu = smp_processor_id();
BUG_ON(!keventd_wq);
- for_each_cpu(cpu) {
- cwq = keventd_wq->cpu_wq + cpu;
- if (current == cwq->thread)
- return 1;
- }
- return 0;
+ cwq = keventd_wq->cpu_wq + cpu;
+ if (current == cwq->thread)
+ return 1;
+ else
+ return 0;
}
----- Forwarded message from Rusty Russell <rusty@rustcorp.com.au> -----
Subject: Re: [lhcs-devel] Re: Kthread_create() never returns when called
from worker_thread
From: Rusty Russell <rusty@rustcorp.com.au>
To: vatsa@in.ibm.com
Cc: rusty@au1.ibm.com,
"Keshavamurthy, Anil S" <anil.s.keshavamurthy@intel.com>,
lhcs-devel@lists.sourceforge.net, "Raj, Ashok" <ashok.raj@intel.com>,
"Shah, Rajesh" <rajesh.shah@intel.com>
X-Mailer: Ximian Evolution 1.4.5
Date: Mon, 08 Mar 2004 11:29:27 +1100
On Wed, 2004-03-03 at 20:08, Srivatsa Vaddagiri wrote:
> On Tue, Mar 02, 2004 at 12:10:08PM +1100, Rusty Russell wrote:
> > /* If we're being called to start the first workqueue, we
> > * can't use keventd. */
> > - if (!keventd_up())
> > + if (!keventd_up() || current_is_keventd())
> > work.func(work.data);
> > else {
> > schedule_work(&work);
>
> I noticed that current_is_keventd() check actually goes and compares
> "current" with all the per-cpu threads attached to keventd() workqueue ..
> Is that really necessary? Can't it compare with the per-cpu thread
> attached to _current_ cpu only?
You'd think so, but it's not my code. I believe you are correct though.
Cheers,
Rusty.
--
Anyone who quotes me in their signature is an idiot -- Rusty Russell
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
lhcs-devel mailing list
lhcs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lhcs-devel
----- End forwarded message -----
--
Thanks and Regards,
Srivatsa Vaddagiri,
Linux Technology Center,
IBM Software Labs,
Bangalore, INDIA - 560017
next reply other threads:[~2004-03-08 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 12:30 Srivatsa Vaddagiri [this message]
2004-03-08 22:36 ` more efficient current_is_keventd macro? [was Re: [lhcs-devel] Re: Kthread_create() never returns when called from worker_thread] Andrew Morton
2004-03-09 1:50 ` Rusty Russell
2004-03-09 13:40 ` Srivatsa Vaddagiri
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=20040308123030.GA7428@in.ibm.com \
--to=vatsa@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rusty@au1.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