lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1349188326.1440.22.camel@anish-Inspiron-N5050>
Date:	Tue, 02 Oct 2012 20:02:06 +0530
From:	anish kumar <anish198519851985@...il.com>
To:	"Pallala, Ramakrishna" <ramakrishna.pallala@...el.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.
> 
> The events I get from two sources are related so I wanted to run my workers and threaded IRQ on single(same) core/cpu.
> 
> Thanks,
> Ram
>  
> 


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ