Commit 9b8eae72 authored by J. Bruce Fields's avatar J. Bruce Fields Committed by Linus Torvalds

Documentation: create new scheduler/ subdirectory

The top-level Documentation/ directory is unmanageably large, so we
should take any obvious opportunities to move stuff into subdirectories.
These sched-*.txt files seem an obvious easy case.
Signed-off-by: default avatarJ. Bruce Fields <bfields@citi.umich.edu>
Cc: Ingo Molnar <mingo@elte.hu>
Acked-by: default avatarRandy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent d3cf91d0
...@@ -332,20 +332,8 @@ rtc.txt ...@@ -332,20 +332,8 @@ rtc.txt
- notes on how to use the Real Time Clock (aka CMOS clock) driver. - notes on how to use the Real Time Clock (aka CMOS clock) driver.
s390/ s390/
- directory with info on using Linux on the IBM S390. - directory with info on using Linux on the IBM S390.
sched-arch.txt scheduler/
- CPU Scheduler implementation hints for architecture specific code. - directory with info on the scheduler.
sched-coding.txt
- reference for various scheduler-related methods in the O(1) scheduler.
sched-design.txt
- goals, design and implementation of the Linux O(1) scheduler.
sched-design-CFS.txt
- goals, design and implementation of the Complete Fair Scheduler.
sched-domains.txt
- information on scheduling domains.
sched-nice-design.txt
- How and why the scheduler's nice levels are implemented.
sched-stats.txt
- information on schedstats (Linux Scheduler Statistics).
scsi/ scsi/
- directory with info on Linux scsi support. - directory with info on Linux scsi support.
serial/ serial/
......
...@@ -11,4 +11,4 @@ Description: ...@@ -11,4 +11,4 @@ Description:
example would be, if User A has shares = 1024 and user example would be, if User A has shares = 1024 and user
B has shares = 2048, User B will get twice the CPU B has shares = 2048, User B will get twice the CPU
bandwidth user A will. For more details refer bandwidth user A will. For more details refer
Documentation/sched-design-CFS.txt Documentation/scheduler/sched-design-CFS.txt
00-INDEX
- this file.
sched-arch.txt
- CPU Scheduler implementation hints for architecture specific code.
sched-coding.txt
- reference for various scheduler-related methods in the O(1) scheduler.
sched-design.txt
- goals, design and implementation of the Linux O(1) scheduler.
sched-design-CFS.txt
- goals, design and implementation of the Complete Fair Scheduler.
sched-domains.txt
- information on scheduling domains.
sched-nice-design.txt
- How and why the scheduler's nice levels are implemented.
sched-stats.txt
- information on schedstats (Linux Scheduler Statistics).
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment