search

AurorWalnut / pyrit

Automatically exported from code.google.com/p/pyrit
0 stars 0 forks source link

ToDo: Separate scheduler from hardware-enumeration #201

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
All hardware-related classes currently live in one module and are 'hacked-in' 
by CPyrit's __init__-function. This is ugly.

Separate the scheduler-code from the hardware-code. The available hardware 
should get enumerated in a persistent way so that users can enable/disable 
devices via configuration. Rename the module 'cpyrit' to 'hardware' (or 
something like that). Create a new class that binds the scheduler to the 
hardware-modules (including auto-configuration).

The hardware-modules need to be modified in order to provide a global unique 
identifier (e.g. PCI-id). Every hardware-related class (e.g. CUDADevice) should 
come with a wrapper-class written in Python to provide an on-top interface.

Original issue reported on code.google.com by lukas.l...@gmail.com on 23 Oct 2010 at 12:12

GoogleCodeExporter commented 8 years ago 
Issue 174 has been merged into this issue.

Original comment by lukas.l...@gmail.com on 23 Oct 2010 at 12:15

GoogleCodeExporter commented 8 years ago 
Issue 237 has been merged into this issue.

Original comment by lukas.l...@gmail.com on 16 Jan 2011 at 9:24

GoogleCodeExporter commented 8 years ago 
My i7 2600 4x 3.4Ghz performs with 4.300 PMKs/s

Original comment by lukas.l...@gmail.com on 11 Feb 2011 at 8:49

GoogleCodeExporter commented 8 years ago 
Issue 317 has been merged into this issue.

Original comment by lukas.l...@gmail.com on 25 May 2011 at 7:26