linux-kernel - [RFC] Static/Runtime CPU/IO bound scheduling polices based on CPU(s) to support complete spectrum of tasks

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-next>] [day] [month] [year] [list]

Message-Id: <1239099931.4773.25.camel@ht.satnam>
Date:	Tue, 07 Apr 2009 15:55:31 +0530
From:	Jaswinder Singh Rajput <jaswinder@...nel.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	David Woodhouse <dwmw2@...radead.org>,
	Peter Zijlstra <peterz@...radead.org>,
	David Miller <davem@...emloft.net>,
	Steven Rostedt <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...nel.org>,
	Andi Kleen <andi@...stfloor.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: [RFC] Static/Runtime CPU/IO bound scheduling polices based on
 CPU(s) to support complete spectrum of tasks

I am planning to prepare the followings:

1. This will be also eligible for UP but more useful for SMPs having
multiple CPUs.

2. Here we can support static/runtime scheduling polices for each CPU
core.

3. Static scheduling polices can be allocated by using command
parameter.

4. In runtime scheduling polices where scheduling polices can be changed
at runtime.

5. Runtime scheduling will be further divided into User defined, Smart
scheduling (automatically by system) and Hybrid scheduling.

6. These scheduling policies can be CPU bound and/or IO bound or others.

7. These scheduling policies can be task based or can be group based say
firefox tasks or multimedia group.

8. By this way we can support complete spectrum of tasks say Non
real-time (NRT), Soft real-time(SRT) and Hard real-time (HRT) tasks.
Like NRT: CPU0, CPU1 and SRT: CPU2 and HRT: CPU3

9. Users can further divide the tasks as NRT, SRT and HRT and can also
change the priorities of each task or group of tasks if they want.

10. In User defined scheduling polices, user can set scheduling polices
for each CPU core at runtime and check what is the performance
(efficiency) of the system.

11. Users can also allocate the scheduling polices per CPU core based on
their requirement and can change it any time.

12. Users can specify which CPUs will work as NRT, SRT and HRT.

13. Users can specify scheduling policies for NRT, SRT and HRT.

14. User will check the performance (efficiency) of the system and also
take suggestion from system that which policy will be better for them.

15. In Smart scheduling policies, system will change the scheduling
polices based on performance (efficiency) of the system to get the
maximum efficiency.

16. Smart scheduling will decide which CPU will work as NRT, SRT and
HRT.

17. Smart scheduling will decide scheduling policies for NRT, SRT and
HRT.

18. In hybrid scheduling where both User defined and Smart scheduling
will work together.

19. In hybrid scheduling, user will define which CPUs will work as User
defined and which CPU will work as Smart scheduling.

20. We can also see the status of the overall system performance and
also based on HRT, SRT and NRT.

Thanks,
--
JSR

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