Timeline for answer to Are Linux kernel modules a sort of Linux system paged pool? by Gilles 'SO- stop being evil'
Current License: CC BY-SA 4.0
Post Revisions
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 22, 2019 at 19:06 | comment | added | Gabriele Scarlatti | yes I know, I just needed to see it stated :) Thanks | |
| Jul 22, 2019 at 19:00 | comment | added | Stephen Kitt | @Gabriele I was only comparing the two, not implying that unloading a kernel module was tied to process execution. When a process exits, its memory is no longer needed and is freed. When a kernel module is unloaded, its memory is no longer needed and is freed. | |
| Jul 22, 2019 at 18:54 | comment | added | Gabriele Scarlatti | @StephenKitt But can kernel module be unloaded during a process execution? or only when the process that uses the module terminate? | |
| Jul 22, 2019 at 18:46 | comment | added | Stephen Kitt | @Gabriele unloading a module releases its memory in the same way that exiting a process does: the memory is no longer needed. Swapping is used with memory pages which are still needed, don’t have their own backing store, and which the kernel decides are better off stored outside of physical memory. | |
| Jul 22, 2019 at 18:39 | comment | added | Gabriele Scarlatti | So essentially process segments can be swapped in and out, while kernel modules can be only loaded and unloaded. The difference seems to be only that when we swap out pages we save what has changed, while a kernel module is just freed when it's sure to be not used again and so no saving is done. Is it that? | |
| Jul 22, 2019 at 18:34 | history | answered | Gilles 'SO- stop being evil' | CC BY-SA 4.0 |