From: NASA Jeff <tallboy258@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Freezing between .48 and .51 when hitting swap.
Date: Sun, 1 Nov 2020 16:20:48 +0000 [thread overview]
Message-ID: <439845F3-9262-4C90-8755-324FA36A28CE@gmail.com> (raw)
I have an issue on my laptop which is old but with 2.5gb of ram an ssd hdd and using zram compression I believe.
When ever it hits swap the system completely locks up and I have to reboot.
This only started occurring in .51
I only have access to my phone at the moment though I’ve looked at the code and have what I believe is a workable solution that should mitigate against and future issues. The code base looked a little old so was probably quite stable but it really could do with some modernisation.
The issue was with the active app in user space.
What needs to be done is to swap out inactive pages in background user apps prior to the active apps hitting the memory threshold which was causing the lockup to occure.
An improvement on the existing code would be to swap in and out inactive pages gradually so as to avoid any heavy system load.
It may also be an idea to set the up priority to near idel for such heavy io background processes so that the overlapping io doesn’t cause issues with user space io.
I believe this is similar to the main Linux scheduler since bfs because implementing a script to renice processes that started hitting higish cpu and then again when their cpu dipped didn’t seem to make much difference. It was unclear if this was also implemented for cocurent io as the window managers now seem to queue io tasks instead of executing them concurrently. Concurrent io was at least a historic issue.
Kind regards,
Oliverthered
Sent from my iPhone
next reply other threads:[~2020-11-01 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 16:20 NASA Jeff [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-01 16:46 Freezing between .48 and .51 when hitting swap NASA Jeff
2020-10-30 4:17 NASA Jeff
2020-11-09 16:57 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=439845F3-9262-4C90-8755-324FA36A28CE@gmail.com \
--to=tallboy258@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).