3 ms·
A complete guide to Linux process scheduling (2015) [pdf]
- LoverKiddo12 4y ago[dead]
- alpha64 4y agoShould append [2015] to the submission title. This is practically ancient news due to the rate of changes in the Linux kernel in this domain.
- janvdberg 4y agoIs there a 2023 version? What parts are obsolete now?
- Ologn 4y agoThe CFS scheduler went into Linux in 2007 and is still the main scheduler, as reflected in this paper, so nothing major has changed in that regard. Most changes are minor. The paper talks about process priority and niceness - a lot of how that works on Unix has not changed in almost fifty years.
- SweetMelody4444 4y ago[dead]
- BadKarma234 4y ago[dead]
- noloblo 4y agoHow does io/uring pollepoll asyncio fit into 2023 Linux user process scheduling? Does this or any other material cover this for rust async await, Python async await?
- anthomtb 4y agoFor your second question, you could write a basic async/await Python or Rust application, then use strace and ftrace to figure out what system calls are happening and what the kernel is doing with them. https://strace.io/ https://strace.io/ https://www.kernel.org/doc/html/v5.0/trace/ftrace.html https://www.kernel.org/doc/html/v5.0/trace/ftrace.html
- deleted 4y ago[deleted]
- pyuser583 4y agoPeople shouldn’t give their pdfs names like “GRADU-1428493916.pdf.”
- Delk 4y agoIt's a thesis from a university publication catalogue, and the file name might be just conforming to some kind of a guideline from their university library. "Gradu" is a common shorthand for "pro gradu" which is the term used in Finland for a master's thesis. The numbers might just be some kind of an id. Many other theses from the same archive also seem to follow some kind of a similar (though not quite identical) pattern in their file names. It's not the most descriptive file name but it might not be the author's choice.
- pyuser583 4y agoI’m not blaming the author at all. But surely the server administrator could map the file path onto a nicer name?