CELF Project Proposal/Add behavior-oriented power management - Revision history

Tim Bird at 23:06, 16 December 2009

2009-12-16T23:06:09Z

Tim Bird: move comments to correct proposal

2009-12-15T00:33:08Z

move comments to correct proposal

Tim Bird: /* Comments */

2009-12-15T00:30:16Z

‎Comments

Tim Bird: /* Comments */ add comment

2009-12-15T00:28:22Z

‎Comments: add comment

Tim Bird: /* Comments */

2009-12-15T00:27:07Z

‎Comments

Tim Bird: Created page with '; Summary : Add behavior-oriented power management ; Proposer : Evgeny Ivashko == Description == Every user has behavioral patterns. Behavioral pattern is the sequence of actio…'

2009-12-15T00:17:41Z

Created page with '; Summary : Add behavior-oriented power management ; Proposer : Evgeny Ivashko == Description == Every user has behavioral patterns. Behavioral pattern is the sequence of actio…'

New page

; Summary : Add behavior-oriented power management

; Proposer : Evgeny Ivashko

== Description ==
Every user has behavioral patterns. Behavioral pattern is the
sequence of actions, running applications and so on. Some of these
patterns are common and the others are individual. Knowing the
patterns the program (that should be developed as the result of the
project) can optimize the OS's behaviour to reduce energy consumption,
response time and etc.

For example (common pattern), if user starts a video in the full-screen
mode the program can automatically suspend some subsystems (like USB or
CD/DVD-rom). Also the program can "hibernate" unused applications.
Another example (individual pattern): if the user usually runs OpenOffice.org
after the game or two of Mahjong, the program can automatically prepare the
OS to quick start of the OOo.

=== Base ===
The work should be based on such technologies as [http://en.wikipedia.org/wiki/Data_Mining Data Mining]
and [http://en.wikipedia.org/wiki/Applied_behavior_analysis Behavior Analysis]

=== Project's objectives ===
The main result of the project should be the program (daemon) that can in
(semi)automatic way change the power and application profiles, that should get
* reducing the device's energy consumption;
* reducing the OS's response time;
* reducing amount of used OS's resources.

== Related work ==
This project should actively use results of such projects as:
* PowerTOP (http://www.lesswatts.org/projects/powertop/)
* BLTK (http://www.lesswatts.org/projects/bltk/)

The approach is well-proven in many different domains (http://en.wikipedia.org/wiki/Data_Mining#Notable_uses).

; Scope : This should take about 6 months.

== Comments ==

[[Category:Project proposals]]

← Older revision		Revision as of 23:06, 16 December 2009
Line 39:		Line 39:

	== Comments ==		== Comments ==
		+	Alexander Voytov wrote:
		+
		+	QNX claims real time power supply management for its car application
		+	embedded solution.
		+
		+	On the PC like laptop/desktop there is the ACPI standard which version
		+	3 I'm not aware is implemented by anyone on any platform. The problem
		+	with the PS(power supply) control is - it is an analog device in the
		+	most common case, but there is a growing market of the digital control
		+	PS. Means, you can control such devices like any other real time
		+	interfaces.
		+
		+	I'm not aware about the PS behaviour control implementation, except
		+	the RF board design. On majority the RFID boards there is a signal
		+	strength pin to power up the board in case the RFID signal is
		+	detected. This is a proprietry design to wake up all board drivers and
		+	interfaces for converting an oncoming analog RF signal into, for
		+	instance, the USB or a serial packet. On some such devices the Linux
		+	kernel is implemented, on majority I'm aware about - the home growth
		+	SW state machine.
		+	----

	[[Category:Project proposals]]		[[Category:Project proposals]]

← Older revision		Revision as of 00:33, 15 December 2009
Line 39:		Line 39:

	== Comments ==		== Comments ==
−	~~Patrick Bellasi writes:~~
−	~~<pre>~~
−	~~That's a really interesting project. Moreover, I think it should be~~
−	~~supported by an OpenSource HW reference platform which is cheap but~~
−	~~sufficiently powerful to replace a semi-professional DAQ.~~
−	~~...~~
−
−	~~I think that the signal acquisition layer should also support the "USB~~
−	~~test and measurement" (TMC) class driver, which is already supported~~
−	~~by Linux: drivers/usb/class/usbtmc.c~~
−	~~</pre>~~
−	~~----~~
−	~~Patrick also wrote:~~
−
−	~~Probably the best one solution out there ''[for an OpenSource HW reference platform]''~~
−	~~I know is the USB-DUXfast,~~
−	~~which is already supported by the COMEDI framework... but is missing~~
−	~~the MTD usb class support.~~
−	~~http://www.linux-usb-daq.co.uk/tech2_duxfast/~~
−	~~The board is relatively cheap compared to the offered features: up to~~
−	~~3MHz continous rate and up to 30MHz in burst mode (256samples),~~
−	~~unfortunately the firmware is not open.~~
−	~~----~~
−	~~Alan Carvalho de Assis wrote:~~
−
−	~~I found this one: http://web.media.mit.edu/~msung/sak2.php~~
−	~~---~~
−

	[[Category:Project proposals]]		[[Category:Project proposals]]

@@ Line 62: / Line 62: @@
 unfortunately the firmware is not open.
 ----
-Alan Carhvalo de Assis wrote:
+Alan Carvalho de Assis wrote:
   I found this one: http://web.media.mit.edu/~msung/sak2.php

@@ Line 62: / Line 62: @@
 unfortunately the firmware is not open.
 ----
 [[Category:Project proposals]]

← Older revision		Revision as of 00:27, 15 December 2009
Line 39:		Line 39:

	== Comments ==		== Comments ==
		+	Patrick Bellasi writes:
		+	<pre>
		+	That's a really interesting project. Moreover, I think it should be
		+	supported by an OpenSource HW reference platform which is cheap but
		+	sufficiently powerful to replace a semi-professional DAQ.
		+	...
		+
		+	I think that the signal acquisition layer should also support the "USB
		+	test and measurement" (TMC) class driver, which is already supported
		+	by Linux: drivers/usb/class/usbtmc.c
		+	</pre>
		+	----
		+	Patrick also wrote:
		+
		+	Probably the best one solution out there ''[for an OpenSource HW reference platform]''
		+	I know is the USB-DUXfast,
		+	which is already supported by the COMEDI framework... but is missing
		+	the MTD usb class support.
		+	http://www.linux-usb-daq.co.uk/tech2_duxfast/
		+	The board is relatively cheap compared to the offered features: up to
		+	3MHz continous rate and up to 30MHz in burst mode (256samples),
		+	unfortunately the firmware is not open.
		+	----
		+
		+

	[[Category:Project proposals]]		[[Category:Project proposals]]