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 for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1249312084.5762.17.camel@sherif-laptop>
Date:	Mon, 03 Aug 2009 18:08:04 +0300
From:	Sherif Fadel <fahmy@...edu>
To:	linux-kernel@...r.kernel.org
Subject: scheduling co-processors

Hi,

I have a dual-core system on which I would like to treat one processor
as a scheduling co-processor. I have already implemented some custom
scheduling policies and tested them with SMP disabled, I would not like
to see if it is possible to have the scheduling algorithm running on one
core and the scheduled tasks running on another.

I do not know if I can somehow use cpus_allowed to restrict the kernel
to one core and the running tasks to another. Is this possible? If so,
could you please inform me how one would go about this?

In case you are wondering why I would need this, I am writing a bunch of
high-overhead distributed scheduling algorithms and I want to mitigate
their overhead in this way.

Thanks.

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