[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <D854C92F57B1B347B57E531E78D05EAD2A26D7@BGSMSX102.gar.corp.intel.com>
Date: Tue, 2 Oct 2012 15:14:22 +0000
From: "Pallala, Ramakrishna" <ramakrishna.pallala@...el.com>
To: anish kumar <anish198519851985@...il.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: How to schedule worker and threaded IRQ on same cpu/core
> On Tue, 2012-10-02 at 12:54 +0000, Pallala, Ramakrishna wrote:
> > > > How can I schedule driver's worker and threaded IRQ on the same core?
> > > >
> > > > For work queue we have schedule_delayed_work_on () API available.
> > > > But how to schedule the threaded IRQ on the same core where my
> > > > worker
> > > thread is going to run?
> > > Why do you need to worry about where your worker thread is going to run?
> > > Or IOW what use case do you have in mind?
> >
> > In my driver I can get two independent events(IRQ and kernel
> > notification). One will be handled by Threaded IRQ and other will be
> > handled by a worker and the order is not guaranteed and with two cores
> Sometimes both workers are being scheduled parallel.
> So what is the problem even if they run in parallel, it would be really help if we
> know what problem you are trying to solve?
> Even if you want to sync between these two then you can have some
> synchronisation mechanism between the two.
> What is the advantage you are going to get if they run on same core?
>
> Sorry but these answers would really help community in resolving your problem.
I think I got what I was looking for...
synchronize_irq()
basically I need to wait/pause my worker thread execution until my threaded handler is complete.
Thanks for response.
Thanks,
Ram
Powered by blists - more mailing lists