Today, first I listened to Shawn share about “All Systemd Go,” a conference attended by Systemd developers. It turns out there really are conferences for every kind of project. This kind of conference for discussing specialized subjects can only be held abroad.
Agenda: KaLUG meetup 2510 - kernel 遇上 user space
It feels like we have been talking about Linux kernel things for two months in a row. It is truly an honor to invite skilled developers to share.
The Linux kernel feature I heard about at today’s KaLuG that is worth looking forward to is the sched_ext project. It includes results contributed by developers from NCKU in Taiwan and was introduced in Linux 6.12. It allows users to change the scheduler from userspace through eBPF, achieving custom scheduling operations. You can even configure cgroups, with each cgroup independently running a different scheduler. In the past, achieving this required recompiling the kernel; after all, there were only so many built-in schedulers. But if clients want to implement their own schedulers for specific work scenarios, upstream obviously cannot accept merging every scheduler. Therefore, this provides an economical method that lets users define their own.
The most intuitive application of sched_ext is improving game performance. CachyOS was the first to build in a mechanism for switching sched_ext. According to the official documentation, they provide multiple scheduler implementations for users to choose from, such as scx_bpfland, which can reduce latency. But some people say Bore Scheduler performs the best. Hmm… this kind of scheduling play probably really requires running very demanding games to measure the difference; otherwise it is just benchmark scores for your own amusement.
Shawn brought a Pi500 computer. So this computer really does look like this. Hmph, I think if it is going to be used as a server, the case should still be as small as possible.
In the middle, so everyone could get to know each other, we gathered around the round table and introduced ourselves one by one. Hmm… I did not have much to mention, so I simply talked about my current professional identity and the Linux distribution I usually use. That’s it. But the official FreeBSD T-shirt I wore seems to have successfully drawn attention.
Speaking of which, from Amos of OCF I learned that people involved in open source projects are not necessarily full-time programmers. That made this script kiddie feel much more reassured and relaxed.
Sunset mentioned that Facebook’s standards for randomly Zucking people are unpredictable, and I deeply agree. The most infuriating part is that Meta’s button for reporting and requesting review is still broken. Whether on Facebook or Threads, it throws errors and does not even let you fill in a reason. The current mechanism retroactively settles scores: for some unknown reason, an old post might violate the rules one day and get taken down, and it might randomly ban a domain. From survivor bias, when you see those low-quality short-video shitposts and scam ads all getting away with it, it really makes you nauseous. These platforms truly do not value digital human rights. It reminds me of someone at KaLuG saying that they posted a late-night snack post and it was successfully maliciously reported… Facebook’s standards are inconsistent. I sincerely hope the AI reviewers and human reviewers’ entire families drop dead. Recently they even hypocritically sent me a user survey, asking whether they were Zucking people too excessively? No shit. I only treat social media messages as temporary places to store information, intended to share the flow of information and guide traffic to other important websites. I do not believe every post can live as long as a blog article. Therefore, this way of thinking is safe. Even if I get Zucked, the psychological sense of loss will not be too great, because all of this is only temporary. I can just skillfully post the same thing again another day. As for self-hosting a Mastodon instance to avoid censorship, even though he claims you can host one with a single Raspberry Pi… I do not have the guts. I will keep parasitizing mastodon.social.
