Linked by cloud on Sat 27th Oct 2012 01:05 UTC
Linux A new version of the real-time Linux scheduler called SCHED_DEADLINE has been released on the Linux Kernel Mailing List. For people who missed previous submissions, it consists of a new deadline-based CPU scheduler for the Linux kernel with bandwidth isolation (resource reservation) capabilities. It supports global/clustered multiprocessor scheduling through dynamic task migrations. This new version takes into account previous comments/suggestions and is aligned to the latest mainline kernel. A video about SCHED_DEADLINE is also available on YouTube.
Thread beginning with comment 540283
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: lie-nux at it again.
by Laurence on Sat 27th Oct 2012 20:12 UTC in reply to "RE: lie-nux at it again."
Laurence
Member since:
2007-03-26

There's a little truth to this. Try running

$ dd if=/dev/zero of=~/dumpfile bs=4G count=1

on a system with 2 GB of RAM and any amount of swap space; the OS will hang for a long, long time.

(If you don't have swap space, the command will fail because you don't have enough memory. But it's not safe to run without swap space... right?)

Mind you, Windows is just as bad about this - it just doesn't have tools like dd preinstalled that can easily crash your computer. ;)


If Linux gets exhausted of RAM, then the requesting application is killed and an OOE (out of memory exception) raised in the event logs.

Sadly this is something I've had to deal with a few times when one idiot web developer decided not to do any input sanitising which effectively ended up with us getting DoS attacked when legitimate users were make innocent page requests. <_<

Reply Parent Score: 3

Gullible Jones Member since:
2006-05-23

If Linux gets exhausted of RAM, then the requesting application is killed and an OOE (out of memory exception) raised in the event logs.

Not quite true, that's what Linux should do. ;) What Linux usually does (unless vm.oom_kill_allocating_task is set to 1) is attempt to kill programs that look like memory hogs, using some kind of heuristic.

In my experience, that heuristic knocks out the offending program about half the time... The other half the time, it knocks out X.

Reply Parent Score: 2

RE[4]: lie-nux at it again.
by Laurence on Sun 28th Oct 2012 11:48 in reply to "RE[3]: lie-nux at it again."
Laurence Member since:
2007-03-26


Not quite true, that's what Linux should do. ;) What Linux usually does (unless vm.oom_kill_allocating_task is set to 1) is attempt to kill programs that look like memory hogs, using some kind of heuristic.

In my experience, that heuristic knocks out the offending program about half the time... The other half the time, it knocks out X.


I stand corrected. Thank you ;)

Reply Parent Score: 2