Overview of Linux real-time challenges
3 likes5,609 views
This document discusses the challenges of real-time computing on Linux and potential solutions. Real-time means very low maximum latency, below 100 microseconds. While Linux was not designed for real-time, it is now used in many embedded systems. Options to address real-time include using separate hardware, a hypervisor with an real-time operating system (RTOS), asymmetric multiprocessing (AMP) with an RTOS, or solutions within Linux like PREEMPT_RT that adds preemption and CPU isolation techniques to reduce worst-case latency without changing applications. The document reviews these approaches and notes that real-time remains an important area as Linux is increasingly used in embedded systems.
1 of 17
Downloaded 39 times
Ad
Recommended
Real time Linux
Real time Linuxnavid ashrafi This slides indicate an introduction on the definition of real time and RTOSes, then you can find information on introducing RT Linux approaches and comparing them with each other, then finally you can see a latency measurement test done by "Linutronix" in the slides
Mastering Real-time Linux
Mastering Real-time LinuxJean-François Deverge This document provides an introduction to real-time systems and discusses approaches to making Linux a real-time operating system. It defines hard and soft real-time systems and explains why Linux is commonly used instead of dedicated real-time operating systems. The document then discusses two main solutions, PREEMPT_RT and Xenomai 3, which provide patches to make Linux meet timing constraints through different approaches. It also provides an overview of basic real-time concepts like scheduling algorithms, preemptive vs. non-preemptive scheduling, and interprocess communication.
HKG15-305: Real Time processing comparing the RT patch vs Core isolation
HKG15-305: Real Time processing comparing the RT patch vs Core isolationLinaro HKG15-305: Real Time processing comparing the RT patch vs Core isolation
---------------------------------------------------
Speaker: Gary Robertson
Date: February 11, 2015
---------------------------------------------------
★ Session Summary ★
Give high level overview of the components involved in a DRM/Secure. Playback use case. Presentation discusses about how Client device obtains License Keys using W3C-EME implementation of any particular DRM like Widevine, how content is decrypted, decoded and rendered and how the buffers are allocated, secured and shared among various elements in the secure playback chain.
--------------------------------------------------
★ Resources ★
Pathable: https://hkg15.pathable.com/meetings/250810
Video: https://www.youtube.com/watch?v=zC3E9xizkoY
Etherpad: http://pad.linaro.org/p/hkg15-305
---------------------------------------------------
★ Event Details ★
Linaro Connect Hong Kong 2015 - #HKG15
February 9-13th, 2015
Regal Airport Hotel Hong Kong Airport
---------------------------------------------------
http://www.linaro.org
http://connect.linaro.org
RT linux
RT linuxSARITHA REDDY RTLinux is a real-time operating system that allows real-time applications to run on top of Linux. It modifies the Linux kernel to add a virtual machine layer with a separate task scheduler that prioritizes real-time tasks over standard Linux processes. This enables RTLinux to support hard real-time deadlines. Programming in RTLinux involves creating modules that can be loaded and unloaded from the kernel using specific commands. Real-time threads and synchronization objects like mutexes are implemented using POSIX interfaces.
Rt linux-lab1
Rt linux-lab1JOLLUSUDARSHANREDDY Real-Time Operating System (RTOS) Vs. General Purpose OS (GPOS)
Can Linux provide real-time guarantees?
Commercial RTOSs
RTLinux Vs. Linux: Architectural comparison
RTLinux Vs. Linux: Code perspective
Get the RTLinux setup ready
Things to Issue and Handling the hard disk
Lab #1: Detailed discussion
Real-time soultion
Real-time soultionNylon This document discusses real-time solutions in Linux. It explains that real-time systems focus on determinism, ensuring events and timing are known. There are several approaches to real-time Linux, including dual kernel systems like RTLinux that run a real-time kernel alongside Linux, and PREEMPT_RT kernels that modify Linux for lower latencies. Popular dual kernel options are RTAI and Xenomai, which provide real-time cores on top of Linux. RTAI focuses on x86 while Xenomai aims to facilitate porting and supports multiple personality "skins". The document provides references for further information on these real-time Linux solutions.
Linux Preempt-RT Internals
Linux Preempt-RT Internals哲豪 康哲豪 Linux PREEMPT_RT improves the preemptiveness of the Linux kernel by allowing preemption everywhere except when preemption is disabled or interrupts are disabled. This reduces latency from preemption, critical sections, and interrupts. However, non-deterministic external interrupt events and timing as well as interrupt collisions can still cause unpredictable latency. Tracing tools can help analyze latency but practical issues remain in fully guaranteeing hard real-time behavior.
Preempt_rt realtime patch
Preempt_rt realtime patchEmre Can Kucukoglu "Controlling a laser with Linux is crazy, but everyone in this room is crazy in his own way. So if you want to use Linux to control an industrial welding laser, I have no problem with your using PREEMPT_RT." -- Linus Torvalds
Real Time Kernels
Real Time KernelsArnav Soni This document summarizes key aspects of real-time kernels. It begins by defining a kernel and its role. It then discusses the structure of a real-time kernel, including layers, states, data structures, and primitives. Scheduling mechanisms like ready queues, insertion, and extraction are covered. Task management, semaphores, and intertask communication using mailboxes and cyclical asynchronous buffers are summarized. The document also discusses system overhead considerations like context switching and interrupts.
Solving Real-Time Scheduling Problems With RT_PREEMPT and Deadline-Based Sche...
Solving Real-Time Scheduling Problems With RT_PREEMPT and Deadline-Based Sche...peknap In dealing with a real world problem of scheduling three classes of tasks – network packet forwarding, voice over IP and application level services for a home gateway device, the author found that mechanisms coming with vanilla Linux kernel are not enough. This talk will cover the unique real-time requirements for each task class, why moving softirq to process context with RT_PREEMPT patch is an important step in solving the problem and how a deadline based process scheduler would be a better solution than regular real-time scheduling classes.
Vx works RTOS
Vx works RTOSSai Malleswar VxWorks is a real-time operating system developed by Wind River Systems that supports ARM, Intel, and other popular processor architectures. It provides a multitasking environment, virtual memory management, networking capabilities, and powerful development tools. VxWorks uses a client-server microkernel architecture and is highly configurable, allowing it to scale from small embedded systems to large networks. It prioritizes real-time deterministic performance and has found widespread use in avionics, medical devices, industrial automation, and other applications.
Testing real-time Linux. What to test and how 
Testing real-time Linux. What to test and how Chirag Jog The document discusses testing of the real-time Linux kernel. It explains that real-time kernel testing focuses on functionality, performance, and latency. Key aspects to test include signal delivery latency, scheduling jitter, and context switch duration. Proper hardware setup and kernel configuration are important. Test cases should run as real-time processes and avoid page faults, disk I/O, and other sources of unpredictable latency when measuring real-time performance.
Real Time Operating Systems
Real Time Operating SystemsPawandeep Kaur This document discusses real-time operating systems (RTOS). It begins by defining an RTOS and distinguishing it from traditional operating systems by its ability to respond to external events in a timely manner. It describes the different types of RTOS based on timing constraints. It then covers key RTOS concepts like preemptive priority scheduling, multitasking, inter-task communication, priority inheritance, and memory management. The document also discusses the Nucleus RTOS and whether RTOS will replace traditional operating systems.
Real Time Operating Systems
Real Time Operating SystemsRohit Joshi - The document discusses real-time systems and concepts, including real-time operating systems. It covers hard and soft real-time systems, task scheduling algorithms like FIFO and priority-based approaches, and requirements for real-time kernels like bounded response times and predictability. The presentation introduces the Nucleus real-time operating system as an example and notes it is a multitasking, preemptive kernel that supports priorities, communication, and synchronization.
Priority Inversion on Mars
Priority Inversion on MarsNational Cheng Kung University The Mars Pathfinder mission successfully demonstrated new landing techniques and returned valuable data from the Martian surface. However, it experienced issues with priority inversion in its VxWorks real-time operating system. The lower priority weather data collection task would occasionally prevent the higher priority communication task from completing before the next cycle began, resetting the system. Engineers traced the problem to the use of VxWorks' select() call to wait for I/O from multiple devices, allowing long-running lower priority tasks to block critical higher priority tasks.
Real-Time Operating Systems
Real-Time Operating SystemsPraveen Penumathsa This document provides an overview of real-time operating systems (RTOS), including their key characteristics, scheduling approaches, and commercial examples. RTOS are used in applications that require tasks to complete work and deliver services on time. They use priority-based and clock-driven scheduling algorithms like rate monotonic analysis and earliest deadline first to ensure real-time constraints are met. Commercial RTOS aim to provide features like priority levels, fast task preemption, and predictable interrupt handling for real-time applications.
RTOS implementation
RTOS implementationRajan Kumar The document discusses real-time operating systems for embedded systems. It describes that RTOS are necessary for systems with scheduling of multiple processes and devices. An RTOS kernel manages tasks, inter-task communication, memory allocation, timers and I/O devices. The document provides examples of creating tasks to blink an LED and print to USART ports, using a semaphore for synchronization between tasks. The tasks are run and output is seen on a Minicom terminal.
Chapter 19 - Real Time Systems
Chapter 19 - Real Time SystemsWayne Jones Jnr System Characteristics
Features of Real-Time Systems
Implementing Real-Time Operating Systems
Real-Time CPU Scheduling
VxWorks 5.x
Real Time Operating system (RTOS) - Embedded systems
Real Time Operating system (RTOS) - Embedded systemsHariharan Ganesan A real-time operating system (RTOS) is an operating system designed for embedded systems where responses need to occur within strict time constraints. An RTOS prioritizes tasks and responds immediately to inputs. There are two types - hard RTOS which must meet deadlines to avoid catastrophic failure, and soft RTOS where occasionally missing deadlines does not cause failure. An RTOS manages tasks, schedules tasks and system resources, and handles interrupts to ensure time-critical applications perform as required.
Real time operating system
Real time operating systemBharti Goyal This document discusses real-time operating systems (RTOS). An RTOS is a data processing system that can process inputs and respond within a small time interval. It ensures tasks are completed within a specified time delay by responding quickly to inputs. RTOS enable multitasking and prioritized process threads. They see widespread use in modern telecommunications, military operations, radar systems, and more. RTOS are either hard real-time systems that guarantee critical tasks finish on time with no virtual memory, or soft real-time systems that prioritize critical tasks over others but are less restrictive and not catastrophic if deadlines are missed.
Vxworks
Vxworksismaeil nethead VxWorks is a real-time operating system (RTOS) that is commonly used in applications that have strict timing requirements. It provides features like multitasking, scheduling, interrupt handling, intertask communication methods like shared memory, message queues, and semaphores. VxWorks uses a layered architecture with a microkernel at its core to provide functions like multiprocessing and POSIX compatibility. It is well-suited for applications in fields like avionics, medical devices, industrial automation, and more where deterministic behavior is important.
Real Time Operating System Concepts
Real Time Operating System ConceptsSanjiv Malik Real-time operating systems (RTOSes) like VxWorks allow for deterministic and fast responses to external events. VxWorks uses multitasking to run applications as separate tasks with inter-task communication. It provides priority-based preemptive multitasking, fast context switching, interrupt handling, and networking capabilities to meet the needs of real-time embedded systems.
Rtos
Rtosseenakumari The document discusses real-time operating systems for networked embedded systems. It provides an example of a fire alarm system using sensors, controllers and a central server connected by low-bandwidth radio links. It then discusses the need for a collaborative action routing solution that is dynamic, auto-configurable and minimizes collisions. The document outlines features of real-time operating systems including scheduling, resource allocation, interrupt handling and targeting various processor architectures.
Rtos concepts
Rtos conceptsanishgoel The document discusses real-time operating systems (RTOS). It defines an RTOS as an operating system intended for real-time applications that must respond to events within strict time constraints. An RTOS has two main components - the "real-time" aspect which ensures responses within deadlines, and the "operating system" aspect which manages hardware resources and allows for multitasking. Common features of RTOSes include task scheduling, synchronization between tasks, and communication between tasks. The document outlines several RTOS concepts such as task management, scheduling, and inter-task communication methods like semaphores.
Rtos part2
Rtos part2navakishore The document summarizes information about real-time operating systems (RTOS). It discusses three real-world examples of issues caused by poor handling of real-time constraints: the Ariane 5 rocket failure due to a floating point exception, the NASA Mars Pathfinder resetting itself, and provides an overview of key RTOS concepts including the kernel, task scheduling, inter-task communication, and device drivers.
Basic functions & types of RTOS ES
Basic functions & types of RTOS ESJOLLUSUDARSHANREDDY This document discusses the basic functions and types of real-time operating systems (RTOS) for embedded systems. It describes key RTOS functions like integrated development environments, timers, scheduling, device drivers, inter-process communication, and memory management. It also categorizes different types of RTOS as in-house developed, broad-based commercial, general purpose OS with RTOS features, and special focus RTOS tailored for specific processors. Overall, the document provides a high-level overview of RTOS functions and classifications.
Making Linux do Hard Real-time
Making Linux do Hard Real-timeNational Cheng Kung University This document discusses making Linux capable of hard real-time performance. It begins by defining hard and soft real-time systems and explaining that real-time does not necessarily mean fast but rather determinism. It then covers general concepts around real-time performance in Linux like preemption, interrupts, context switching, and scheduling. Specific features in Linux like RT-Preempt, priority inheritance, and threaded interrupts that improve real-time capabilities are also summarized.
presentation on real time operating system(RTOS's)
presentation on real time operating system(RTOS's)chetan mudenoor Real time Operating Systems are very fast and quick respondent systems. These systems are used in an environment where a large number of events (generally external) must be accepted and processed in a short time.
Making Linux do Hard Real-time
Making Linux do Hard Real-timeNational Cheng Kung University This presentation covers the general concepts about real-time systems, how Linux kernel works for preemption, the latency in Linux, rt-preempt, and Xenomai, the real-time extension as the dual kernel approach.
Modellflyg med open source
Modellflyg med open sourcebjornhaxx This document discusses model aircraft built with open source components. It describes common types of model aircraft like planes and helicopters, how they are controlled with radio transmitters and receivers, and how first person view (FPV) systems allow pilots to see what the aircraft sees in real time. Open source autopilot, navigation, and camera systems that can be used are also outlined. Specific component recommendations are provided.
Ad
More Related Content
What's hot (20)
Real Time Kernels
Real Time KernelsArnav Soni This document summarizes key aspects of real-time kernels. It begins by defining a kernel and its role. It then discusses the structure of a real-time kernel, including layers, states, data structures, and primitives. Scheduling mechanisms like ready queues, insertion, and extraction are covered. Task management, semaphores, and intertask communication using mailboxes and cyclical asynchronous buffers are summarized. The document also discusses system overhead considerations like context switching and interrupts.
Solving Real-Time Scheduling Problems With RT_PREEMPT and Deadline-Based Sche...
Solving Real-Time Scheduling Problems With RT_PREEMPT and Deadline-Based Sche...peknap In dealing with a real world problem of scheduling three classes of tasks – network packet forwarding, voice over IP and application level services for a home gateway device, the author found that mechanisms coming with vanilla Linux kernel are not enough. This talk will cover the unique real-time requirements for each task class, why moving softirq to process context with RT_PREEMPT patch is an important step in solving the problem and how a deadline based process scheduler would be a better solution than regular real-time scheduling classes.
Vx works RTOS
Vx works RTOSSai Malleswar VxWorks is a real-time operating system developed by Wind River Systems that supports ARM, Intel, and other popular processor architectures. It provides a multitasking environment, virtual memory management, networking capabilities, and powerful development tools. VxWorks uses a client-server microkernel architecture and is highly configurable, allowing it to scale from small embedded systems to large networks. It prioritizes real-time deterministic performance and has found widespread use in avionics, medical devices, industrial automation, and other applications.
Testing real-time Linux. What to test and how
Testing real-time Linux. What to test and how Chirag Jog The document discusses testing of the real-time Linux kernel. It explains that real-time kernel testing focuses on functionality, performance, and latency. Key aspects to test include signal delivery latency, scheduling jitter, and context switch duration. Proper hardware setup and kernel configuration are important. Test cases should run as real-time processes and avoid page faults, disk I/O, and other sources of unpredictable latency when measuring real-time performance.
Real Time Operating Systems
Real Time Operating SystemsPawandeep Kaur This document discusses real-time operating systems (RTOS). It begins by defining an RTOS and distinguishing it from traditional operating systems by its ability to respond to external events in a timely manner. It describes the different types of RTOS based on timing constraints. It then covers key RTOS concepts like preemptive priority scheduling, multitasking, inter-task communication, priority inheritance, and memory management. The document also discusses the Nucleus RTOS and whether RTOS will replace traditional operating systems.
Real Time Operating Systems
Real Time Operating SystemsRohit Joshi - The document discusses real-time systems and concepts, including real-time operating systems. It covers hard and soft real-time systems, task scheduling algorithms like FIFO and priority-based approaches, and requirements for real-time kernels like bounded response times and predictability. The presentation introduces the Nucleus real-time operating system as an example and notes it is a multitasking, preemptive kernel that supports priorities, communication, and synchronization.
Priority Inversion on Mars
Priority Inversion on MarsNational Cheng Kung University The Mars Pathfinder mission successfully demonstrated new landing techniques and returned valuable data from the Martian surface. However, it experienced issues with priority inversion in its VxWorks real-time operating system. The lower priority weather data collection task would occasionally prevent the higher priority communication task from completing before the next cycle began, resetting the system. Engineers traced the problem to the use of VxWorks' select() call to wait for I/O from multiple devices, allowing long-running lower priority tasks to block critical higher priority tasks.
Real-Time Operating Systems
Real-Time Operating SystemsPraveen Penumathsa This document provides an overview of real-time operating systems (RTOS), including their key characteristics, scheduling approaches, and commercial examples. RTOS are used in applications that require tasks to complete work and deliver services on time. They use priority-based and clock-driven scheduling algorithms like rate monotonic analysis and earliest deadline first to ensure real-time constraints are met. Commercial RTOS aim to provide features like priority levels, fast task preemption, and predictable interrupt handling for real-time applications.
RTOS implementation
RTOS implementationRajan Kumar The document discusses real-time operating systems for embedded systems. It describes that RTOS are necessary for systems with scheduling of multiple processes and devices. An RTOS kernel manages tasks, inter-task communication, memory allocation, timers and I/O devices. The document provides examples of creating tasks to blink an LED and print to USART ports, using a semaphore for synchronization between tasks. The tasks are run and output is seen on a Minicom terminal.
Chapter 19 - Real Time Systems
Chapter 19 - Real Time SystemsWayne Jones Jnr System Characteristics
Features of Real-Time Systems
Implementing Real-Time Operating Systems
Real-Time CPU Scheduling
VxWorks 5.x
Real Time Operating system (RTOS) - Embedded systems
Real Time Operating system (RTOS) - Embedded systemsHariharan Ganesan A real-time operating system (RTOS) is an operating system designed for embedded systems where responses need to occur within strict time constraints. An RTOS prioritizes tasks and responds immediately to inputs. There are two types - hard RTOS which must meet deadlines to avoid catastrophic failure, and soft RTOS where occasionally missing deadlines does not cause failure. An RTOS manages tasks, schedules tasks and system resources, and handles interrupts to ensure time-critical applications perform as required.
Real time operating system
Real time operating systemBharti Goyal This document discusses real-time operating systems (RTOS). An RTOS is a data processing system that can process inputs and respond within a small time interval. It ensures tasks are completed within a specified time delay by responding quickly to inputs. RTOS enable multitasking and prioritized process threads. They see widespread use in modern telecommunications, military operations, radar systems, and more. RTOS are either hard real-time systems that guarantee critical tasks finish on time with no virtual memory, or soft real-time systems that prioritize critical tasks over others but are less restrictive and not catastrophic if deadlines are missed.
Vxworks
Vxworksismaeil nethead VxWorks is a real-time operating system (RTOS) that is commonly used in applications that have strict timing requirements. It provides features like multitasking, scheduling, interrupt handling, intertask communication methods like shared memory, message queues, and semaphores. VxWorks uses a layered architecture with a microkernel at its core to provide functions like multiprocessing and POSIX compatibility. It is well-suited for applications in fields like avionics, medical devices, industrial automation, and more where deterministic behavior is important.
Real Time Operating System Concepts
Real Time Operating System ConceptsSanjiv Malik Real-time operating systems (RTOSes) like VxWorks allow for deterministic and fast responses to external events. VxWorks uses multitasking to run applications as separate tasks with inter-task communication. It provides priority-based preemptive multitasking, fast context switching, interrupt handling, and networking capabilities to meet the needs of real-time embedded systems.
Rtos
Rtosseenakumari The document discusses real-time operating systems for networked embedded systems. It provides an example of a fire alarm system using sensors, controllers and a central server connected by low-bandwidth radio links. It then discusses the need for a collaborative action routing solution that is dynamic, auto-configurable and minimizes collisions. The document outlines features of real-time operating systems including scheduling, resource allocation, interrupt handling and targeting various processor architectures.
Rtos concepts
Rtos conceptsanishgoel The document discusses real-time operating systems (RTOS). It defines an RTOS as an operating system intended for real-time applications that must respond to events within strict time constraints. An RTOS has two main components - the "real-time" aspect which ensures responses within deadlines, and the "operating system" aspect which manages hardware resources and allows for multitasking. Common features of RTOSes include task scheduling, synchronization between tasks, and communication between tasks. The document outlines several RTOS concepts such as task management, scheduling, and inter-task communication methods like semaphores.
Rtos part2
Rtos part2navakishore The document summarizes information about real-time operating systems (RTOS). It discusses three real-world examples of issues caused by poor handling of real-time constraints: the Ariane 5 rocket failure due to a floating point exception, the NASA Mars Pathfinder resetting itself, and provides an overview of key RTOS concepts including the kernel, task scheduling, inter-task communication, and device drivers.
Basic functions & types of RTOS ES
Basic functions & types of RTOS ESJOLLUSUDARSHANREDDY This document discusses the basic functions and types of real-time operating systems (RTOS) for embedded systems. It describes key RTOS functions like integrated development environments, timers, scheduling, device drivers, inter-process communication, and memory management. It also categorizes different types of RTOS as in-house developed, broad-based commercial, general purpose OS with RTOS features, and special focus RTOS tailored for specific processors. Overall, the document provides a high-level overview of RTOS functions and classifications.
Making Linux do Hard Real-time
Making Linux do Hard Real-timeNational Cheng Kung University This document discusses making Linux capable of hard real-time performance. It begins by defining hard and soft real-time systems and explaining that real-time does not necessarily mean fast but rather determinism. It then covers general concepts around real-time performance in Linux like preemption, interrupts, context switching, and scheduling. Specific features in Linux like RT-Preempt, priority inheritance, and threaded interrupts that improve real-time capabilities are also summarized.
presentation on real time operating system(RTOS's)
presentation on real time operating system(RTOS's)chetan mudenoor Real time Operating Systems are very fast and quick respondent systems. These systems are used in an environment where a large number of events (generally external) must be accepted and processed in a short time.
Viewers also liked (11)
Making Linux do Hard Real-time
Making Linux do Hard Real-timeNational Cheng Kung University This presentation covers the general concepts about real-time systems, how Linux kernel works for preemption, the latency in Linux, rt-preempt, and Xenomai, the real-time extension as the dual kernel approach.
Modellflyg med open source
Modellflyg med open sourcebjornhaxx This document discusses model aircraft built with open source components. It describes common types of model aircraft like planes and helicopters, how they are controlled with radio transmitters and receivers, and how first person view (FPV) systems allow pilots to see what the aircraft sees in real time. Open source autopilot, navigation, and camera systems that can be used are also outlined. Specific component recommendations are provided.
curl and new technologies
curl and new technologiesDaniel Stenberg These are the slides from the talk Daniel Stenberg did at the foss-sthlm meetup 12 on March 5 2013 in Stockholm Sweden.
Ineffective and Effective Ways To Find Out Latency Bottlenecks With Ftrace
Ineffective and Effective Ways To Find Out Latency Bottlenecks With FtraceYoshitake Kobayashi The document discusses using Ftrace to identify latency bottlenecks. It provides an example where cyclictest is showing high scheduling latency but the cause is unknown. The author then demonstrates how to use Ftrace to analyze two cases. In the first case, no other workload is present and latency is low. In the second case, a shell is run with high priority, interfering with cyclictest and causing high latency. Ftrace trace logs are examined to identify the shell as the source of the latency.
An Essential Relationship between Real-time and Resource Partitioning
An Essential Relationship between Real-time and Resource PartitioningYoshitake Kobayashi (ELC Europe 2013)
Running real-time and general purpose applications on a same hardware is normally a crazy idea in most case. However, we strongly focus to run both applications on a hardware without virtualization. Resource Partitioning enables the assignment of hardware resource (e.g.: core, execution time, memory bandwidth or device access) to processes with special requirements (e.g: real-time performance or safety requirements).
In this talk, we would like to discuss current limitation on Linux kernel and describe how to solve it.
Improvement of Scheduling Granularity for Deadline Scheduler 
Improvement of Scheduling Granularity for Deadline Scheduler Yoshitake Kobayashi (Embedded Linux Conference Europe 2012)
https://github.com/ystk/sched-deadline/tree/dlmiss-detection-dev
Real-time system need to meet deadline. In this point of view, the system is required two functions to have determinism. One is interruptlatency stabilization and the other one is processing time reservation. The SCHED_DEADLINE has a feature to reserve CPU time in advance to ensure predictable behavior. In our evaluation, the granularity of CPU reservation is millisecond order.In this presentation, we show the evaluation results of current implementation to make clear the issue. Then we explain how to overcome this issue and its results.
Real-time system need to meet deadline. In this point of view, the system is required two functions to have determinism. One is interruptlatency stabilization and the other one is processing time reservation. The SCHED_DEADLINE has a feature to reserve CPU time in advance to ensure predictable behavior. In our evaluation, the granularity of CPU reservation is millisecond order.In this presentation, we show the evaluation results of current implementation to make clear the issue. Then we explain how to overcome this issue and its results.
F9: A Secure and Efficient Microkernel Built for Deeply Embedded Systems
F9: A Secure and Efficient Microkernel Built for Deeply Embedded SystemsNational Cheng Kung University F9 is a new open source microkernel designed for deeply embedded systems like IoT devices. It aims to provide efficiency, security, and a flexible development environment. F9 follows microkernel principles with minimal kernel functionality and isolates components as user-level processes. It uses capabilities for access control and focuses on performance through techniques like tickless scheduling and adaptive power management.
Linux Performance Analysis: New Tools and Old Secrets
Linux Performance Analysis: New Tools and Old SecretsBrendan Gregg Talk for USENIX/LISA2014 by Brendan Gregg, Netflix. At Netflix performance is crucial, and we use many high to low level tools to analyze our stack in different ways. In this talk, I will introduce new system observability tools we are using at Netflix, which I've ported from my DTraceToolkit, and are intended for our Linux 3.2 cloud instances. These show that Linux can do more than you may think, by using creative hacks and workarounds with existing kernel features (ftrace, perf_events). While these are solving issues on current versions of Linux, I'll also briefly summarize the future in this space: eBPF, ktap, SystemTap, sysdig, etc.
Broken Linux Performance Tools 2016
Broken Linux Performance Tools 2016Brendan Gregg Broken benchmarks, misleading metrics, and terrible tools. This talk will help you navigate the treacherous waters of Linux performance tools, touring common problems with system tools, metrics, statistics, visualizations, measurement overhead, and benchmarks. You might discover that tools you have been using for years, are in fact, misleading, dangerous, or broken.
The speaker, Brendan Gregg, has given many talks on tools that work, including giving the Linux PerformanceTools talk originally at SCALE. This is an anti-version of that talk, to focus on broken tools and metrics instead of the working ones. Metrics can be misleading, and counters can be counter-intuitive! This talk will include advice for verifying new performance tools, understanding how they work, and using them successfully.
Linux Performance Analysis and Tools
Linux Performance Analysis and ToolsBrendan Gregg Video: http://joyent.com/blog/linux-performance-analysis-and-tools-brendan-gregg-s-talk-at-scale-11x ; This talk for SCaLE11x covers system performance analysis methodologies and the Linux tools to support them, so that you can get the most out of your systems and solve performance issues quickly. This includes a wide variety of tools, including basics like top(1), advanced tools like perf, and new tools like the DTrace for Linux prototypes.
Linux 4.x Tracing: Performance Analysis with bcc/BPF
Linux 4.x Tracing: Performance Analysis with bcc/BPFBrendan Gregg Talk about bcc/eBPF for SCALE15x (2017) by Brendan Gregg. "BPF (Berkeley Packet Filter) has been enhanced in the Linux 4.x series and now powers a large collection of performance analysis and observability tools ready for you to use, included in the bcc (BPF Complier Collection) open source project. BPF nowadays can do system tracing, software defined networks, and kernel fast path: much more than just filtering packets! This talk will focus on the bcc/BPF tools for performance analysis, which make use of other built in Linux capabilities: dynamic tracing (kprobes and uprobes) and static tracing (tracepoints and USDT). There are now bcc tools for measuring latency distributions for file system I/O and run queue latency, printing details of storage device I/O and TCP retransmits, investigating blocked stack traces and memory leaks, and a whole lot more. These lead to performance wins large and small, especially when instrumenting areas that previously had zero visibility. Tracing superpowers have finally arrived, built in to Linux."
F9: A Secure and Efficient Microkernel Built for Deeply Embedded Systems
F9: A Secure and Efficient Microkernel Built for Deeply Embedded SystemsNational Cheng Kung University
Ad
Similar to Overview of Linux real-time challenges (20)
Choosing the right parallel compute architecture 
Choosing the right parallel compute architecture corehard_by Multi-core architecture is the present and future way in which the market is addressing Moore’s law limitations. Multi-core workstations, high performance computers, GPUs and the focus on hybrid/ public cloud technologies for offloading and scaling applications is the direction development is heading. Leveraging multiple cores in order to increase application performance and responsiveness is expected especially from classic high-throughput executions such as rendering, simulations, and heavy calculations. Choosing the correct multi-core strategy for your software requirements is essential, making the wrong decision can have serious implications on software performance, scalability, memory usage and other factors. In this overview, we will inspect various considerations for choosing the correct multi-core strategy for your application’s requirement and investigate the pros and cons of multi-threaded development vs multi-process development. For example, Boost’s GIL (Generic Image Library) provides you with the ability to efficiently code image processing algorithms. However, deciding whether your algorithms should be executed as multi-threaded or multi-process has a high impact on your design, coding, future maintenance, scalability, performance, and other factors.
A partial list of considerations to take into account before taking this architectural decision includes:
- How big are the images I need to process
- What risks can I have in terms of race-conditions, timing issues, sharing violations – does it justify multi-threading programming?
- Do I have any special communication and synchronization requirements?
- How much time would it take my customers to execute a large scenario?
- Would I like to scale processing performance by using the cloud or cluster?
We will then examine these issues in real-world environments. In order to learn how this issue is being addressed in a real-world scenario, we will examine common development and testing environments we are using in our daily work and compare the multi-core strategies they have implemented in order to promote higher development productivity.
Dori Exterman, Considerations for choosing the parallel computing strategy th...
Dori Exterman, Considerations for choosing the parallel computing strategy th...Sergey Platonov This document discusses strategies for parallel computing and implications of different approaches. It covers multi-threaded versus multi-process development and considerations for each. Multi-threaded development allows for easy data sharing but risks crashing entire processes if one thread fails, while multi-process is more scalable but requires custom communication between processes. The document also provides examples of scenarios that may be better suited for multi-threaded or multi-process approaches based on factors like task dependencies, data and memory requirements, and scalability needs.
DDoS Mitigator. Personal control panel for each hosting clients.
DDoS Mitigator. Personal control panel for each hosting clients.Глеб Хохлов The document discusses the need for a DDoS mitigation solution given the increasing frequency and sophistication of DDoS attacks. It proposes a solution called "Mitigator" that gives site administrators control over DDoS protection for their services by observing attacks and manipulating the protection process when needed. Mitigator is designed as a physical or virtual appliance with high-performance hardware and software for inline or out-of-band deployment to provide layered DDoS protection for hosting and data center customers.
Deep Dive into the Idea of Software Architecture
Deep Dive into the Idea of Software ArchitectureMatthew Clarke This talk was an experiment in combining a number of ideas I'd been learning and thinking about into a coherent presentation, that would hopefully be useful. The was to give a solid grounding to the idea of software architecture, including taking a critical look at what it is and if it really matters. It then moves into the topics of boundaries and abstractions, horizontal and vertical layers, cross-cutting concerns, "Clean Architecture" and the Dependency Rule it rests upon. It was presented internally at Genesis Energy in September 2018.
Non-Functional Requirements
Non-Functional RequirementsDavid Simons Understanding what a Non-Funcitonal Requirement (NFR) is, introducing some key kinds of NFR and looking at what we can do to solve them
BYOD Revisited: Build Your Own Device (Embedded Linux Conference 2014)
BYOD Revisited: Build Your Own Device (Embedded Linux Conference 2014)Ron Munitz This document summarizes Ron Munitz's presentation on building devices for BYOD (Build Your Own Device) at the Embedded Linux Conference 2014. It discusses the history of embedded systems and operating systems. It then covers rapid prototyping techniques using evaluation boards to begin software development before the custom hardware is ready. This allows demonstrating proofs of concept and checking functionality while the hardware is being manufactured. Modern operating systems like Linux, Android and Tizen can run on evaluation boards, with the software then ported to the custom hardware once it is complete. Rapid prototyping cycles help accelerate the process and integrate hardware and software teams.
ISHOT 2.0 - Easy Life with Internet of Things
ISHOT 2.0 - Easy Life with Internet of ThingsAlwin Arrasyid This document discusses how Internet of Things (IoT) technologies can provide an easy life for both consumers and engineers. It provides examples of IoT products like SmartGallon and Magic Button that make life easier through automation and notifications. For engineers, it recommends using the right development tools like ESP32 boards, programming languages, and cloud services to efficiently build IoT solutions. The key takeaways are that automation prevents unnecessary tasks, saves time and resources, and notifying users when they need to take action can also improve the user experience.
Go programming language
Go programming languageAppstud Après la présentation de #Flutter, Julien nous révèle toute la puissance de #Go, encore un autre langage de programmation créé par Google.
After the #Flutter presentation, Julien reveals all the power of #Go, yet another programming language created by Google.
2 years into drinking the Microservice kool-aid (Fact and Fiction)
2 years into drinking the Microservice kool-aid (Fact and Fiction)roblund This document discusses microservices and continuous deployment strategies using microservices. It describes the characteristics of microservices like being independently deployable and scalable. Some benefits mentioned include resilience, zero downtime upgrades, and independent scaling. The document then discusses some challenges of microservices like complex communication between services and testing strategies. It provides examples of canary testing deployments and how microservices allow continuous deployment. Finally, it discusses lessons learned around using multiple communication protocols and ensuring ordered messaging between microservices.
Do more, code less with parallel computing libraries
Do more, code less with parallel computing librariesJie Fu The document discusses parallel computing libraries that allow users to accelerate MATLAB code using GPUs without having to write GPU-specific code, and how parallel computing can help address challenges in machine learning by allowing users to focus on solving machine learning problems rather than dealing with parallelization issues across different hardware architectures. It also discusses the need for high-level abstractions that can simplify the design of parallel machine learning programs to handle graph-based dependencies, iterative computations, and asynchronous execution across distributed systems.
CS101- Introduction to Computing- Lecture 45
CS101- Introduction to Computing- Lecture 45Bilal Ahmed This lecture provides a review and wrap-up of the CS101 Introduction to Computing course. It summarizes key topics covered over the past 44 lectures such as programming methodology, readable code, algorithm design, testing and debugging. It reviews objectives of the course which were to build an appreciation of fundamental computing concepts, familiarize students with popular productivity software, and achieve beginner proficiency in web development. The lecture concludes by asking for student feedback on how well the course objectives were achieved.
Summer project- Jack Fletcher 
Summer project- Jack Fletcher Jack Fletcher Jack Fletcher discusses how computer hardware, software, networking, and society have shaped the modern world and will continue to do so in the future. He describes how early computers like the Colossus were developed during World War II and how hardware has rapidly advanced, with smartphones now having more power than the computers on Apollo rockets. Fletcher also explains how software is built, different types of software, and how networking allows for file sharing, online gaming, and more. Finally, he discusses how these technologies have transformed daily life and will bring developments like 4K displays, 3D printing, and online streaming.
Microservice architecture
Microservice architectureŽilvinas Kuusas Microservice architecture. Short intro into the world of microservices, the talk I gave in VilniusPHP meetup.
“Deploying Large Language Models on a Raspberry Pi,” a Presentation from Usef...
“Deploying Large Language Models on a Raspberry Pi,” a Presentation from Usef...Edge AI and Vision Alliance For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/07/deploying-large-language-models-on-a-raspberry-pi-a-presentation-from-useful-sensors/
Pete Warden, CEO of Useful Sensors, presents the “Deploying Large Language Models on a Raspberry Pi,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, Warden outlines the key steps required to implement a large language model (LLM) on a Raspberry Pi. He begins by outlining the motivations for running LLMs on the edge and exploring practical use cases for LLMs at the edge. Next, he provides some rules of thumb for selecting hardware to run an LLM.
Warden then walks through the steps needed to adapt an LLM for an application using prompt engineering and LoRA retraining. He demonstrates how to build and run an LLM from scratch on a Raspberry Pi. Finally, he shows how to integrate an LLM with other edge system building blocks, such as a speech recognition engine to enable spoken input and application logic to trigger actions.
Mobile Single Source Strategy
Mobile Single Source StrategyRaja Nagendra Kumar The document discusses the challenges of developing mobile applications for enterprises. It notes the issues with current development models, including high costs, long development times, and difficulties supporting new devices. It introduces TejaSoft's Mobile Development Framework (TezzMDF) which aims to address these challenges through a single source approach that eliminates device-specific code and simplifies adding support for new devices. TezzMDF is presented as a potential solution to help enterprises reduce mobile application development costs and time to market.
Meetup 2020 - Back to the Basics part 101 : IaC
Meetup 2020 - Back to the Basics part 101 : IaCDamienCarpy Slides first played during meetup at Devoteam on March, 3rd 2020
https://www.meetup.com/fr-FR/Cloud-Devops-Devoteam/events/268904319/
What is Reactive programming?
What is Reactive programming?Kevin Webber A general overview of Reactive programming, including the history of Reactive application development and why this paradigm is the right fit for developing modern software. Explores examples from JavaScript, Scala, Erlang, and Akka.
OTTO-multicloud
OTTO-multicloudOtto (GmbH & Co KG) This document discusses the pros and cons of a multicloud approach versus using a single cloud provider. It acknowledges that while a multicloud strategy is important for reducing vendor lock-in, in practice it may be better for new teams to start with AWS due to existing knowledge and support structures. The document provides guidance on how to adopt a multicloud approach over time while still allowing individual teams to choose the cloud provider that best fits their current needs and experience.
Rakuten Ichiba_Rakuten Technology Conference 2016
Rakuten Ichiba_Rakuten Technology Conference 2016Rakuten Group, Inc. ●Overall introduction of Ichiba
Introduction
●Redis Cluster in Rakuten Ichiba
How we use Redis Cluster in Rakuten Ichiba
●R Framework
The challenge of updating a legacy system sharing code between multiple teams, using an in-house developed library for the Rakuten Ichiba Frontend side.
●Rakuten Catalog Platform- Classification Approach for 280,000,000 Ichiba items -
1. Taxonomy Strategy(Analyze, Adoption)
2. Rakuten Catalog Platform Classification Ichiba Item data -> Taxonomy(Taxonomy(Genre/Tag/Attribute) management/development) -> Catalog(Product Master) -> Data governance system -> Data Processing Unit -> Auto classification(Item information/Image)
●How to reconstruct a million-user app
Describes why we decided to rewrite our app, what difficulties we faced and how we create the new structure to ensure it's flexible, stable and maintainable.
https://tech.rakuten.co.jp/
Modeling on the Web
Modeling on the WebIcinetic Modeling Software on the browser provides great benefits like zero deployment and multi-device. However providing modeling infrastructure on the browser require entering in the JavaScript world to create all the infrastructure needed. In this talk, such infrastructure for textual, projectional and diagram DSLs are discused. Session presented at Code Generation 2014.
“Deploying Large Language Models on a Raspberry Pi,” a Presentation from Usef...
“Deploying Large Language Models on a Raspberry Pi,” a Presentation from Usef...Edge AI and Vision Alliance
Ad
More from Daniel Stenberg (20)
What comes after world domination with Daniel Stenberg, April 2025
What comes after world domination with Daniel Stenberg, April 2025Daniel Stenberg Open Source has in many ways already won. It is used in every product by every company, to a very a large degree. But we are not done. We can improve: we can take this further, we can make our projects better, we can enhance our communities and make sure it is done sustainably. The future is ours.
digital infrastruktur är open source-1.pdf
digital infrastruktur är open source-1.pdfDaniel Stenberg Idag är all digital infrastruktur baserad på och innehåller Open Source til en väldigt hög grad. Varför, hur funkar det, vem gör det etc.
Tightening every bolt at FOSDEM 2025 by Daniel Stenberg
Tightening every bolt at FOSDEM 2025 by Daniel StenbergDaniel Stenberg Things to do in order to sleep well while having your C code in twenty billion installations. A talk about what the curl project does to minimize security risks: Security, Safety, Reproducibility, Vulnerability handling and the processes and tooling around it.
As BDFL of the curl project, Daniel talks about what this project does to avoid it causing the world to burn. From code style, reviews and tests to signings, reproducibility, running a bug-bounty and becoming a CNA to filter bogus CVEs. curl aims to be top of the class in (Open Source) software security. Here's your chance to point finger and tell us what we should do better.
curl security by Daniel Stenberg from curl up 2024
curl security by Daniel Stenberg from curl up 2024Daniel Stenberg The state of curl security in 2024 from curl up 2024.
rust in curl by Daniel Stenberg from- curl up 2024
rust in curl by Daniel Stenberg from- curl up 2024Daniel Stenberg Daniel talks about using rust components in curl, at curl up 2024
trurl 2024 by Daniel Stenberg from curl up 2024
trurl 2024 by Daniel Stenberg from curl up 2024Daniel Stenberg Daniel speaks about the trurl command line tool at curl up 2024.
curl future 2024 by Daniel Stenberg from curl up 2024
curl future 2024 by Daniel Stenberg from curl up 2024Daniel Stenberg Daniel speaks about what's coming next in the curl project. From curl up 2024.
The state of curl 2024 by Daniel Stenberg from curl up 2024
The state of curl 2024 by Daniel Stenberg from curl up 2024Daniel Stenberg Daniel talks about the state of the project.
mastering libcurl part 2
mastering libcurl part 2Daniel Stenberg This document discusses using libcurl's share API to share data like cookies and DNS caches between multiple easy handles. It explains that some curl state is kept in the easy handle, so transfers using different handles may not be fully independent. The share API allows creating share objects that specify what data to share, such as cookies and DNS caches. Easy handles can then specify which share objects to use to share data between transfers and achieve better performance than using separate handles independently.
mastering libcurl part 1
mastering libcurl part 1Daniel Stenberg Mastering libcurl (1/2)
The project, get libcurl, build it, API and ABI, Architecture, API fundamentals and details on Setting up transfer things.
curl - openfourm europe.pdf
curl - openfourm europe.pdfDaniel Stenberg Daniel Stenberg's keynote at the Openforum Europe event "Open Source Driving the European Digital Decade" on April 18, 2023
curl experiments - curl up 2022
curl experiments - curl up 2022Daniel Stenberg We have various pieces of code marked EXPERIMENTAL. What parts and what's the status now? Is it time to remove the label from parts?
curl security - curl up 2022
curl security - curl up 2022Daniel Stenberg This document discusses curl security practices such as continuous integration testing on many platforms, custom test servers, tools used for analysis like Valgrind and Clang sanitizers, and "torture tests" that inject errors. It notes that while testing all combinations is impossible, common setups and architectures are tested. The curl bug bounty program is mentioned as paying $40,900 so far. An upcoming code audit and ensuring decreasing CVEs and fuzzing reports over time are discussed as signs the efforts are working. Recent CVE trends and introductions like "dynbuf" are also summarized.
HTTP/3 in curl - curl up 2022
HTTP/3 in curl - curl up 2022Daniel Stenberg - What's new in QUIC and HTTP/3
- How it's glued into curl
- How to build curl to use it
- How to use it with libcurl
at curl up 2022
The state of curl 2022
The state of curl 2022Daniel Stenberg For curl up 2022, Daniel summarizes the past year, what the curl project did, what it does and maybe what it will do next.
Let me tell you about curl
Let me tell you about curlDaniel Stenberg This document provides an overview of curl, an open source command line tool and library for transferring data with Internet protocols. It discusses curl's history starting in 1998, its widespread usage across operating systems, CPU architectures, and planets. It also outlines curl's many supported features and protocols, large number of contributors and commits, extensive testing, and commitment to security and open development. The future of curl is discussed in the context of the growing Internet of Things and connectivity of everyday devices and appliances.
Curl with rust
Curl with rustDaniel Stenberg Daniel Stenberg gave a presentation on using Rust with curl. He discussed how curl has traditionally used C but now supports alternative backends implemented in other languages like Rust. He described challenges in integrating the Hyper, rustls, and quiche Rust crates but curl now supports HTTP/1-2 with Hyper and TLS with rustls in an experimental way. Future work includes improving test coverage when using Rust backends and potentially enabling them by default.
Getting started with libcurl
Getting started with libcurlDaniel Stenberg Daniel Stenberg goes through some basic libcurl fundamentals and API design and explain how easily you can get your first transfers going in your own application. libcurl is the defacto standard library for Internet transfers and runs on virtually all platforms. The language focus will be on C/C++ but the concepts are generally applicable even if you use libcurl bindings for other languages.
HTTP/3 is next generation HTTP
HTTP/3 is next generation HTTPDaniel Stenberg A presentation about HTTP/3 and QUIC done by Daniel Stenberg at the GOTOpia conference in November 2020.
Landing code in curl
Landing code in curlDaniel Stenberg Daniel Stenberg takes us through the steps and shows and explains how easy it is to have your code contributions landed in curl.
Recently uploaded (20)
Transcript: #StandardsGoals for 2025: Standards & certification roundup - Tec...
Transcript: #StandardsGoals for 2025: Standards & certification roundup - Tec...BookNet Canada Book industry standards are evolving rapidly. In the first part of this session, we’ll share an overview of key developments from 2024 and the early months of 2025. Then, BookNet’s resident standards expert, Tom Richardson, and CEO, Lauren Stewart, have a forward-looking conversation about what’s next.
Link to recording, presentation slides, and accompanying resource: https://bnctechforum.ca/sessions/standardsgoals-for-2025-standards-certification-roundup/
Presented by BookNet Canada on May 6, 2025 with support from the Department of Canadian Heritage.
Foundations of Cybersecurity - Google Certificate
Foundations of Cybersecurity - Google CertificateVICTOR MAESTRE RAMIREZ Foundations of Cybersecurity - Google Certificate
HCL Nomad Web – Best Practices und Verwaltung von Multiuser-Umgebungen
HCL Nomad Web – Best Practices und Verwaltung von Multiuser-Umgebungenpanagenda Webinar Recording: https://www.panagenda.com/webinars/hcl-nomad-web-best-practices-und-verwaltung-von-multiuser-umgebungen/
HCL Nomad Web wird als die nächste Generation des HCL Notes-Clients gefeiert und bietet zahlreiche Vorteile, wie die Beseitigung des Bedarfs an Paketierung, Verteilung und Installation. Nomad Web-Client-Updates werden “automatisch” im Hintergrund installiert, was den administrativen Aufwand im Vergleich zu traditionellen HCL Notes-Clients erheblich reduziert. Allerdings stellt die Fehlerbehebung in Nomad Web im Vergleich zum Notes-Client einzigartige Herausforderungen dar.
Begleiten Sie Christoph und Marc, während sie demonstrieren, wie der Fehlerbehebungsprozess in HCL Nomad Web vereinfacht werden kann, um eine reibungslose und effiziente Benutzererfahrung zu gewährleisten.
In diesem Webinar werden wir effektive Strategien zur Diagnose und Lösung häufiger Probleme in HCL Nomad Web untersuchen, einschließlich
- Zugriff auf die Konsole
- Auffinden und Interpretieren von Protokolldateien
- Zugriff auf den Datenordner im Cache des Browsers (unter Verwendung von OPFS)
- Verständnis der Unterschiede zwischen Einzel- und Mehrbenutzerszenarien
- Nutzung der Client Clocking-Funktion
How analogue intelligence complements AI
How analogue intelligence complements AIPaul Rowe
Artificial Intelligence is providing benefits in many areas of work within the heritage sector, from image analysis, to ideas generation, and new research tools. However, it is more critical than ever for people, with analogue intelligence, to ensure the integrity and ethical use of AI. Including real people can improve the use of AI by identifying potential biases, cross-checking results, refining workflows, and providing contextual relevance to AI-driven results.
News about the impact of AI often paints a rosy picture. In practice, there are many potential pitfalls. This presentation discusses these issues and looks at the role of analogue intelligence and analogue interfaces in providing the best results to our audiences. How do we deal with factually incorrect results? How do we get content generated that better reflects the diversity of our communities? What roles are there for physical, in-person experiences in the digital world?
Reimagine How You and Your Team Work with Microsoft 365 Copilot.pptx
Reimagine How You and Your Team Work with Microsoft 365 Copilot.pptxJohn Moore M365 Community Conference 2025 Workshop on Microsoft 365 Copilot
Transcript: Canadian book publishing: Insights from the latest salary survey ...
Transcript: Canadian book publishing: Insights from the latest salary survey ...BookNet Canada Join us for a presentation in partnership with the Association of Canadian Publishers (ACP) as they share results from the recently conducted Canadian Book Publishing Industry Salary Survey. This comprehensive survey provides key insights into average salaries across departments, roles, and demographic metrics. Members of ACP’s Diversity and Inclusion Committee will join us to unpack what the findings mean in the context of justice, equity, diversity, and inclusion in the industry.
Results of the 2024 Canadian Book Publishing Industry Salary Survey: https://publishers.ca/wp-content/uploads/2025/04/ACP_Salary_Survey_FINAL-2.pdf
Link to presentation slides and transcript: https://bnctechforum.ca/sessions/canadian-book-publishing-insights-from-the-latest-salary-survey/
Presented by BookNet Canada and the Association of Canadian Publishers on May 1, 2025 with support from the Department of Canadian Heritage.
Enterprise Integration Is Dead! Long Live AI-Driven Integration with Apache C...
Enterprise Integration Is Dead! Long Live AI-Driven Integration with Apache C...Markus Eisele We keep hearing that “integration” is old news, with modern architectures and platforms promising frictionless connectivity. So, is enterprise integration really dead? Not exactly! In this session, we’ll talk about how AI-infused applications and tool-calling agents are redefining the concept of integration, especially when combined with the power of Apache Camel.
We will discuss the the role of enterprise integration in an era where Large Language Models (LLMs) and agent-driven automation can interpret business needs, handle routing, and invoke Camel endpoints with minimal developer intervention. You will see how these AI-enabled systems help weave business data, applications, and services together giving us flexibility and freeing us from hardcoding boilerplate of integration flows.
You’ll walk away with:
An updated perspective on the future of “integration” in a world driven by AI, LLMs, and intelligent agents.
Real-world examples of how tool-calling functionality can transform Camel routes into dynamic, adaptive workflows.
Code examples how to merge AI capabilities with Apache Camel to deliver flexible, event-driven architectures at scale.
Roadmap strategies for integrating LLM-powered agents into your enterprise, orchestrating services that previously demanded complex, rigid solutions.
Join us to see why rumours of integration’s relevancy have been greatly exaggerated—and see first hand how Camel, powered by AI, is quietly reinventing how we connect the enterprise.
TrsLabs - Leverage the Power of UPI Payments
TrsLabs - Leverage the Power of UPI PaymentsTrs Labs Revolutionize your Fintech growth with UPI Payments
"Riding the UPI strategy" refers to leveraging the Unified Payments Interface (UPI) to drive digital payments in India and beyond. This involves understanding UPI's features, benefits, and potential, and developing strategies to maximize its usage and impact. Essentially, it's about strategically utilizing UPI to promote digital payments, financial inclusion, and economic growth.
Play It Safe: Manage Security Risks - Google Certificate
Play It Safe: Manage Security Risks - Google CertificateVICTOR MAESTRE RAMIREZ Play It Safe: Manage Security Risks - Google Certificate
Hybridize Functions: A Tool for Automatically Refactoring Imperative Deep Lea...
Hybridize Functions: A Tool for Automatically Refactoring Imperative Deep Lea...Raffi Khatchadourian Efficiency is essential to support responsiveness w.r.t. ever-growing datasets, especially for Deep Learning (DL) systems. DL frameworks have traditionally embraced deferred execution-style DL code—supporting symbolic, graph-based Deep Neural Network (DNN) computation. While scalable, such development is error-prone, non-intuitive, and difficult to debug. Consequently, more natural, imperative DL frameworks encouraging eager execution have emerged but at the expense of run-time performance. Though hybrid approaches aim for the “best of both worlds,” using them effectively requires subtle considerations to make code amenable to safe, accurate, and efficient graph execution—avoiding performance bottlenecks and semantically inequivalent results. We discuss the engineering aspects of a refactoring tool that automatically determines when it is safe and potentially advantageous to migrate imperative DL code to graph execution and vice-versa.
Vaibhav Gupta BAML: AI work flows without Hallucinations
Vaibhav Gupta BAML: AI work flows without Hallucinationsjohn409870 Shipping Agents
Vaibhav Gupta
Cofounder @ Boundary
in/vaigup
boundaryml/baml
Imagine if every API call you made
failed only 5% of the time
boundaryml/baml
Imagine if every LLM call you made
failed only 5% of the time
boundaryml/baml
Imagine if every LLM call you made
failed only 5% of the time
boundaryml/baml
Fault tolerant systems are hard
but now everything must be
fault tolerant
boundaryml/baml
We need to change how we
think about these systems
Aaron Villalpando
Cofounder @ Boundary
Boundary
Combinator
boundaryml/baml
We used to write websites like this:
boundaryml/baml
But now we do this:
boundaryml/baml
Problems web dev had:
boundaryml/baml
Problems web dev had:
Strings. Strings everywhere.
boundaryml/baml
Problems web dev had:
Strings. Strings everywhere.
State management was impossible.
boundaryml/baml
Problems web dev had:
Strings. Strings everywhere.
State management was impossible.
Dynamic components? forget about it.
boundaryml/baml
Problems web dev had:
Strings. Strings everywhere.
State management was impossible.
Dynamic components? forget about it.
Reuse components? Good luck.
boundaryml/baml
Problems web dev had:
Strings. Strings everywhere.
State management was impossible.
Dynamic components? forget about it.
Reuse components? Good luck.
Iteration loops took minutes.
boundaryml/baml
Problems web dev had:
Strings. Strings everywhere.
State management was impossible.
Dynamic components? forget about it.
Reuse components? Good luck.
Iteration loops took minutes.
Low engineering rigor
boundaryml/baml
React added engineering rigor
boundaryml/baml
The syntax we use changes how we
think about problems
boundaryml/baml
We used to write agents like this:
boundaryml/baml
Problems agents have:
boundaryml/baml
Problems agents have:
Strings. Strings everywhere.
Context management is impossible.
Changing one thing breaks another.
New models come out all the time.
Iteration loops take minutes.
boundaryml/baml
Problems agents have:
Strings. Strings everywhere.
Context management is impossible.
Changing one thing breaks another.
New models come out all the time.
Iteration loops take minutes.
Low engineering rigor
boundaryml/baml
Agents need
the expressiveness of English,
but the structure of code
F*** You, Show Me The Prompt.
boundaryml/baml
<show don’t tell>
Less prompting +
More engineering
=
Reliability +
Maintainability
BAML
Sam
Greg Antonio
Chris
turned down
openai to join
ex-founder, one
of the earliest
BAML users
MIT PhD
20+ years in
compilers
made his own
database, 400k+
youtube views
Vaibhav Gupta
in/vaigup
vbv@boundaryml.com
boundaryml/baml
Thank you!
GyrusAI - Broadcasting & Streaming Applications Driven by AI and ML
GyrusAI - Broadcasting & Streaming Applications Driven by AI and MLGyrus AI Gyrus AI: AI/ML for Broadcasting & Streaming
Gyrus is a Vision Al company developing Neural Network Accelerators and ready to deploy AI/ML Models for Video Processing and Video Analytics.
Our Solutions:
Intelligent Media Search
Semantic & contextual search for faster, smarter content discovery.
In-Scene Ad Placement
AI-powered ad insertion to maximize monetization and user experience.
Video Anonymization
Automatically masks sensitive content to ensure privacy compliance.
Vision Analytics
Real-time object detection and engagement tracking.
Why Gyrus AI?
We help media companies streamline operations, enhance media discovery, and stay competitive in the rapidly evolving broadcasting & streaming landscape.
🚀 Ready to Transform Your Media Workflow?
🔗 Visit Us: https://gyrus.ai/
📅 Book a Demo: https://gyrus.ai/contact
📝 Read More: https://gyrus.ai/blog/
🔗 Follow Us:
LinkedIn - https://www.linkedin.com/company/gyrusai/
Twitter/X - https://twitter.com/GyrusAI
YouTube - https://www.youtube.com/channel/UCk2GzLj6xp0A6Wqix1GWSkw
Facebook - https://www.facebook.com/GyrusAI
Unlocking Generative AI in your Web Apps
Unlocking Generative AI in your Web AppsMaximiliano Firtman Slides for the session delivered at Devoxx UK 2025 - Londo.
Discover how to seamlessly integrate AI LLM models into your website using cutting-edge techniques like new client-side APIs and cloud services. Learn how to execute AI models in the front-end without incurring cloud fees by leveraging Chrome's Gemini Nano model using the window.ai inference API, or utilizing WebNN, WebGPU, and WebAssembly for open-source models.
This session dives into API integration, token management, secure prompting, and practical demos to get you started with AI on the web.
Unlock the power of AI on the web while having fun along the way!
The No-Code Way to Build a Marketing Team with One AI Agent (Download the n8n...
The No-Code Way to Build a Marketing Team with One AI Agent (Download the n8n...SOFTTECHHUB The No-Code Way to Build a Marketing Team with One AI Agent (Download the n8n Template Free)
How to Install & Activate ListGrabber - eGrabber
How to Install & Activate ListGrabber - eGrabbereGrabber ListGrabber: Build Targeted Lists Online in Minutes
Canadian book publishing: Insights from the latest salary survey - Tech Forum...
Canadian book publishing: Insights from the latest salary survey - Tech Forum...BookNet Canada Join us for a presentation in partnership with the Association of Canadian Publishers (ACP) as they share results from the recently conducted Canadian Book Publishing Industry Salary Survey. This comprehensive survey provides key insights into average salaries across departments, roles, and demographic metrics. Members of ACP’s Diversity and Inclusion Committee will join us to unpack what the findings mean in the context of justice, equity, diversity, and inclusion in the industry.
Results of the 2024 Canadian Book Publishing Industry Salary Survey: https://publishers.ca/wp-content/uploads/2025/04/ACP_Salary_Survey_FINAL-2.pdf
Link to presentation recording and transcript: https://bnctechforum.ca/sessions/canadian-book-publishing-insights-from-the-latest-salary-survey/
Presented by BookNet Canada and the Association of Canadian Publishers on May 1, 2025 with support from the Department of Canadian Heritage.
UiPath Automation Suite – Cas d'usage d'une NGO internationale basée à Genève
UiPath Automation Suite – Cas d'usage d'une NGO internationale basée à GenèveUiPathCommunity Nous vous convions à une nouvelle séance de la communauté UiPath en Suisse romande.
Cette séance sera consacrée à un retour d'expérience de la part d'une organisation non gouvernementale basée à Genève. L'équipe en charge de la plateforme UiPath pour cette NGO nous présentera la variété des automatisations mis en oeuvre au fil des années : de la gestion des donations au support des équipes sur les terrains d'opération.
Au délà des cas d'usage, cette session sera aussi l'opportunité de découvrir comment cette organisation a déployé UiPath Automation Suite et Document Understanding.
Cette session a été diffusée en direct le 7 mai 2025 à 13h00 (CET).
Découvrez toutes nos sessions passées et à venir de la communauté UiPath à l’adresse suivante : https://community.uipath.com/geneva/.
Hybridize Functions: A Tool for Automatically Refactoring Imperative Deep Lea...
Hybridize Functions: A Tool for Automatically Refactoring Imperative Deep Lea...Raffi Khatchadourian
Overview of Linux real-time challenges
- 2. Daniel Stenberg Email: daniel@haxx.se Twitter: @bagder Web: daniel.haxx.se Blog: daniel.haxx.se/blog ● Free Software ● Network hacker ● Embedded developer ● Consultant
- 3. Agenda What's real-time in this context? Why is real-time still a concern? Ways to deal with the problem • Off to secondary hardware • Hypervisor or AMP • PREEMPT_RT • CPU isolation and dynamic tick Future?
- 4. Realtime Real-time can mean a lot of different things to different audiences • Low maximum latency: below 100 us, sometimes down to 20us • Very low risk of every breaking that
- 5. Why is this a concern 2013? • Plain Linux wasn't designed to deal with low latency • A move towards "commodity" hardware - less special stuff means solving the problems in general CPUs • Linux everywhere: RTOS-solutions get moved over from legacy systems to Linux-based • Still a lot of stacks and applications that act in CPU but needs to respond fast and accurately • Sometimes a bit more requested than perhaps can be technically motivated
- 6. What are the options? Linux is a given. What magic can you apply to a system to address the problem of a low maximum latency?
- 7. Separate dedicated HW • A tested and proven way • A separate small chip (with an RTOS?) for just the time critical stuff • ... or an FPGA • But it adds system complexity and price
- 8. Hypervisor with RTOS • Isn't pure Linux • Adds complexity • Usually proprietary • May reach really low latencies One or more cores
- 9. AMP with RTOS • Isn't pure Linux • Adds complexity • Often proprietary • May reach really low latencies Core 0 Core 1 Core 2 Core 3
- 10. The more pure Linux solutions 1 Address and lower the worst case 2 Avoid hitting the worst case
- 13. Linux kernel Core 0 Core 1 Core 2 Core 3 CPU isolation 2/2
- 15. (from UBM Tech Electronics' Embedded Market Survery)
- 16. Work with this at Enea