* [patch] SCHED_SOFTRR linux scheduler policy ... @ 2003-07-10 2:33 Davide Libenzi 2003-07-13 11:50 ` Pavel Machek 0 siblings, 1 reply; 5+ messages in thread From: Davide Libenzi @ 2003-07-10 2:33 UTC (permalink / raw) To: Linux Kernel Mailing List I finally found a couple of hours for this and I also found a machine were I can run 2.5, since luck abandoned myself about this. The small page describe the obvious and contain the trivial patch and the latecy test app : http://www.xmailserver.org/linux-patches/softrr.html - Davide ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [patch] SCHED_SOFTRR linux scheduler policy ... 2003-07-10 2:33 [patch] SCHED_SOFTRR linux scheduler policy Davide Libenzi @ 2003-07-13 11:50 ` Pavel Machek 2003-07-13 11:53 ` Alan Cox 2003-07-13 16:08 ` [patch] SCHED_SOFTRR linux scheduler policy Davide Libenzi 0 siblings, 2 replies; 5+ messages in thread From: Pavel Machek @ 2003-07-13 11:50 UTC (permalink / raw) To: Davide Libenzi; +Cc: Linux Kernel Mailing List Hi! > I finally found a couple of hours for this and I also found a machine were > I can run 2.5, since luck abandoned myself about this. The small page > describe the obvious and contain the trivial patch and the latecy test app : > > http://www.xmailserver.org/linux-patches/softrr.html What happens if evil user forks 60 processes, marks them all SCHED_SOFTRR, and tries to starve everyone else? Pavel -- When do you have a heart between your knees? [Johanka's followup: and *two* hearts?] ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [patch] SCHED_SOFTRR linux scheduler policy ... 2003-07-13 11:50 ` Pavel Machek @ 2003-07-13 11:53 ` Alan Cox 2003-07-13 18:13 ` Scheduler woes ( was [patch] SCHED_SOFTRR linux scheduler policy) Davide Libenzi 2003-07-13 16:08 ` [patch] SCHED_SOFTRR linux scheduler policy Davide Libenzi 1 sibling, 1 reply; 5+ messages in thread From: Alan Cox @ 2003-07-13 11:53 UTC (permalink / raw) To: Pavel Machek; +Cc: Davide Libenzi, Linux Kernel Mailing List On Sul, 2003-07-13 at 12:50, Pavel Machek wrote: > Hi! > > > I finally found a couple of hours for this and I also found a machine were > > I can run 2.5, since luck abandoned myself about this. The small page > > describe the obvious and contain the trivial patch and the latecy test app : > > > > http://www.xmailserver.org/linux-patches/softrr.html > > What happens if evil user forks 60 processes, marks them all > SCHED_SOFTRR, and tries to starve everyone else? With the current scheduler you lose. Rik did some playing with a fair share scheduler some time ago. That actually works very well for a lot of these sorts of things. You can nice processes up (but only by penalising your own processes) and conceptually you'd be able to soft real time on a per user basis this way. Alan ^ permalink raw reply [flat|nested] 5+ messages in thread
* Scheduler woes ( was [patch] SCHED_SOFTRR linux scheduler policy) ... 2003-07-13 11:53 ` Alan Cox @ 2003-07-13 18:13 ` Davide Libenzi 0 siblings, 0 replies; 5+ messages in thread From: Davide Libenzi @ 2003-07-13 18:13 UTC (permalink / raw) To: Alan Cox; +Cc: Ingo Molnar, Linux Kernel Mailing List On Sun, 13 Jul 2003, Alan Cox wrote: > On Sul, 2003-07-13 at 12:50, Pavel Machek wrote: > > Hi! > > > > > I finally found a couple of hours for this and I also found a machine were > > > I can run 2.5, since luck abandoned myself about this. The small page > > > describe the obvious and contain the trivial patch and the latecy test app : > > > > > > http://www.xmailserver.org/linux-patches/softrr.html > > > > What happens if evil user forks 60 processes, marks them all > > SCHED_SOFTRR, and tries to starve everyone else? > > With the current scheduler you lose. Rik did some playing with a fair > share scheduler some time ago. That actually works very well for a lot > of these sorts of things. You can nice processes up (but only by > penalising your own processes) and conceptually you'd be able to soft > real time on a per user basis this way. There are currently two kind of problems, that can be solved with different approaches. One is starvation and the other one is fairness among system users. Googling around for problems reported about starvation, we can find stuff reported by David Mosberger plus other real or artificial piece of code that makes the scheduler to starve other tasks (or at least assign CPU slices in a way less than optimal way). Since Ingo will be listening I'll go with some ideas. I believe we should have three domains inside the scheduler 1) RT 2) Interactive 3) Non-Interactive, having three different priority lists. It is possible to have 1 and 2 collapsed to restrict the schema to a dual-domain. The algorithm should be like : if ((t = get_rt_task()) != NULL) goto got_it; if (time_to_pick_interactive() && (t = get_int_task()) != NULL) goto got_it; if (!(t = get_nint_task())) t = idle(); got_it: ... Functions get_*() do the std bitmap lookup and O(1) fetch. The function time_to_pick_interactive() is a trivial function of the time consumed by interactive tasks and non-interactive tasks so that we can even eventually tune it with /proc. Even a super-trivial policy like : static inline int time_to_pick_interactive(void) { return rt->sched_num % N; } would work. Even with N very small like 2, the greater timeslice allocated for interactive tasks will still assign a huge slice of CPU to them (a quadratic of cubic timeslice(prio) function will mark even more the gap). The EXPIRED_STARVING() thing simply does not work, expecially with a ten second setup. Also, it makes all interactive tasks to fall trough in the expired array. The above solution will guarantee that no starvation will be experienced by other tasks. You really want to make time_to_pick_interactive() a function of the allocated CPU time to achieve a better distribution. All the tricks available to hit the interactive selection machanism will fail under this solution. All non-iteractive tasks will have their *guaranteed* (and tunable) minimum CPU time. You can easily keep the time allocation information inside the run queue struct so that you can access them w/out extra locks. Ingo, I know you're busy with other stuff but you should definitely take a look at some of the exposed cases, some of them are scary if you think at what they can do in a multi-user environment. - Davide ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [patch] SCHED_SOFTRR linux scheduler policy ... 2003-07-13 11:50 ` Pavel Machek 2003-07-13 11:53 ` Alan Cox @ 2003-07-13 16:08 ` Davide Libenzi 1 sibling, 0 replies; 5+ messages in thread From: Davide Libenzi @ 2003-07-13 16:08 UTC (permalink / raw) To: Pavel Machek; +Cc: Linux Kernel Mailing List On Sun, 13 Jul 2003, Pavel Machek wrote: > Hi! > > > I finally found a couple of hours for this and I also found a machine were > > I can run 2.5, since luck abandoned myself about this. The small page > > describe the obvious and contain the trivial patch and the latecy test app : > > > > http://www.xmailserver.org/linux-patches/softrr.html > > What happens if evil user forks 60 processes, marks them all > SCHED_SOFTRR, and tries to starve everyone else? Oh, no doubt you can do it. The SOFTRR thing can be fixed for this, pretty easily. The problem, like Alan is saying, is that with the current scheduler you do not need SOFTRR to starve other tasks. This is why I said that all the issues that have been grought up in the last few months should be discussed before going in 2.6. So that we can either say that are corner cases that we can ive ith, or we fix them. I didn't follow the scheduler after the first merge but it seems that a couple of issues should be addressed before 2.6. - Davide ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2003-07-13 18:05 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2003-07-10 2:33 [patch] SCHED_SOFTRR linux scheduler policy Davide Libenzi 2003-07-13 11:50 ` Pavel Machek 2003-07-13 11:53 ` Alan Cox 2003-07-13 18:13 ` Scheduler woes ( was [patch] SCHED_SOFTRR linux scheduler policy) Davide Libenzi 2003-07-13 16:08 ` [patch] SCHED_SOFTRR linux scheduler policy Davide Libenzi
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®