The Linux Kernel Mailing List
 help / color / mirror / Atom feed
* more efficient current_is_keventd macro? [was Re: [lhcs-devel] Re: Kthread_create() never returns when called from worker_thread]
@ 2004-03-08 12:30 Srivatsa Vaddagiri
  2004-03-08 22:36 ` Andrew Morton
  0 siblings, 1 reply; 4+ messages in thread
From: Srivatsa Vaddagiri @ 2004-03-08 12:30 UTC (permalink / raw)
  To: mingo; +Cc: rusty, linux-kernel

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2004-03-09 13:39 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-08 12:30 more efficient current_is_keventd macro? [was Re: [lhcs-devel] Re: Kthread_create() never returns when called from worker_thread] Srivatsa Vaddagiri
2004-03-08 22:36 ` Andrew Morton
2004-03-09  1:50   ` Rusty Russell
2004-03-09 13:40   ` Srivatsa Vaddagiri

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox