• 8 Posts
  • 82 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle









  • I’m trying to find some of the old videos that I watched, but it’s really hard! I guess that kind of content disappears quickly beneath the thousands of similar videos.

    One of my favorites back then was a dude on his expensive BMW motorcycle traveling India, and in the chaotic traffic there he had a small crash and it bent his fork, and he also got a hairline fracture on his ankle, I believe.

    So, the x-ray machines in the hospital was too bad to image that fracture. So that went untreated and caused him a looot of discomfort. Also, almost nobody in India rides such expensive BMW bikes, so it took him aaages and crazy amounts of money to get a spare part for that bike shipped from Germany, and to find a tech that could install it. It was excellent suffering born from luxury. Can recommend.









  • Look what I just did:

    "In a real-time kernel, the trouble with using print_k (or similar logging functions) often revolves around potential disruptions to real-time performance. Here are some key issues:

    1. Blocking Behavior: print_k may block if the output buffer is full, leading to unpredictable delays in real-time tasks.

    2. Interrupt Context: Using logging functions within interrupt handlers can lead to priority inversion, causing lower-priority tasks to block higher-priority ones.

    3. Latency: Printing can introduce significant latency, which is detrimental in real-time systems that require deterministic timing.

    4. Context Switching: Frequent logging can increase context switching overhead, impacting overall system performance.

    5. Overhead: The computational overhead of formatting and outputting strings can interfere with time-sensitive operations.

    For these reasons, it’s typically recommended to use alternative methods, such as circular buffers for logging, or to minimize logging in real-time contexts.

    "