SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
And congratulations for involuntary great demonstration of how can be made a proprietary program with source code available.
Yes, a program published without a license, automatically is considered having a proprietary license where "all rights are reserved" to author. This happens at least on America, Europa and Asia.
For Copyright to apply, a work is required to be non-trivial and/or have an element of originality about it. I don't think we need worry here.
About a half-decade ago I was using Slackware on an old slow computer with not much memory, and I saw similar:
Quote:
Originally Posted by dchmelik
[...] I had significant desktop lag for years/decades using Slackware even after disabling animations, most effects, and upgrading to new hardware (compared to DOS-based even on a 486) [...]
I also disabled animations and 'effects' and whatnot --- but even so, from time to time the computer would start thrashing and the processor(s) would become 100% busy. One day an idea came to me that perhaps the user software was impeding the kernel. So, I ran
Code:
renice -n 10 -u <my usersname>
This worked well, and after a while I added the command into my user's ".xinitrc" file.
The change logs and tarballs for kernel updates 5.14.15, 5.10.76, 5.4.156, 4.19.214, 4.14.253, 4.9.288 and 4.4.290 are now available at, https://www.kernel.org
Looks like the patch for setting the default dynamic preempt mode has landed in the kernel tip tree. Unless I am mistaken that means it will eventually make its way into the kernel.
Looks like the patch for setting the default dynamic preempt mode has landed in the kernel tip tree. Unless I am mistaken that means it will eventually make its way into the kernel.
Yes, BUT this looks like that it will be added on the kernel 5.16.x so, those will want it in previous versions, they should backport it.
So, did you see our BDFL backporting this patch to 5.14.x or 5.15.x, when he invented that one-liner sed command which basicaly do a similar job at build time ?
Last edited by LuckyCyborg; 10-27-2021 at 10:56 AM.
Yes, BUT this looks like that it will be added on the kernel 5.16.x so, those will want it in previous versions, they should backport it.
So, did you see our BDFL backporting this patch to 5.14.x or 5.15.x, when he invented that one-liner sed command which basicaly do a similar job at build time ?
Yeah the default preempt=full issue is easily worked around. I am just noting that it looks like they did listen to people complaining about the lack of a changeable default option and fixed it.
This assumes the parameters are processed in a normal fashion, some parameters (dyndbg= for example) don't register their parameter with the rest of the kernel's parameters, and therefore always show up in this list (and are also given to init - like the rest of this list).
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,006
Rep:
I wonder why not to compile preemptible kernel with full preempt for desktop?
Then other options can be tweaked e.g. RCU, hugepage and so on and so for
plus all GCC tweaks can also help with the performance.
I never had problems with stuttering even under load but I never used default Slackware kernel.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.