 as an operating system in embedded (even consumer) applications because of its easy adaptability to a variety of processors and cus- tomization-enabled by being open-source in nature and potentially free of cost. Embedded versions of Linux are often stripped-down for unneeded features including the GUI and Chapter 5 System software application support. This compactness and optimization of features to the application is what defines the embedded implementation of Linux. By implication of being small, com- pute requirements and implementation cost (say, disk size) are contained (but not necessar- ily small as they would be in a microcontroller environment). As Linux is gaining popularity not only in server and consumer PC application but also in an embedded environment, we observed that SIMD capabilities give modern General-Purpose cores reasonable "number crunching" capabilities as required to implement L1 processing. These two factors (Linux becoming an embedded capable os and Moore's law supporting general-purpose processors becoming capable DSPs) define the popularity of Software Defined Networking in general and O-RAN in particular. However, there is a challenge on how to support the latency and os overhead challenges associated with using standard Linux as a development and deployment framework, repla- cing a typical DSP Implementation that heavily relies on custom RTOS environments designed to be low latency. In fact, there are several challenges to be solved: Challenge 1: Operating System response time for real time applications 3GPP protocol implementation requires deterministic timing to slot and symbol bound- aries, whereas Linux has been built to be a general-purpose operating system, not optimized for real time. There are a few different ways of tackling the os latency topic in real time scheduling environments: Cokernel approaches (such as Xenomai) which are an alternative to PREEMPT_RT and allow the system a more realtime behavior. In different implementation-specific ways, there approaches combine 