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: <D854C92F57B1B347B57E531E78D05EAD2A1EE5@BGSMSX102.gar.corp.intel.com>
Date:	Tue, 2 Oct 2012 12:54:55 +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

> > 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.

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
 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ