A message for Linux.com registered users: We are in the process of making changes to the Linux forums. Starting Monday, 8/13/18 at 6:00 PM PT, you will be unable to access the forums. They will re-launch as soon as possible on Wednesday, 8/15/18 with new features and improved functionality. Thank you for your patience and stay tuned for the new improved forums.
Understanding the Linux kernel development
I just posted on a general "Software Development" forum about open technology that trivializes handling architecturally or otherwise structured code blocks dynamically.
I would like to understand the guidance challenges in critical Kernel sections as well as not-so-critical yet often modified portions of parametrized values to alter the kernel build.
This technology allows flexible use of recognizing and guiding about architectural structures (such as kernel-scheduler) that can be tailored independently even by the very novice Linuxians, who just happen to understand scheduling perfectly and know exactly what parameters or alterations the scheduler requires to suit for their embedded/real-time usage.
I hope I can get somewhat active dialogue around the subject, as while the technology is open and platform-agnostic, we have little understanding about Linux kernel development on our own. We understand operating systems and their architectural structures, but we need someone with experience on Linux Kernel, who can show the reference implementations that we can then together help to abstract out.