USDT Tracing Report

Total Page:16

File Type:pdf, Size:1020Kb

USDT Tracing Report USDT Tracing report Dale Hamel 06/27/20 10:06:13 PM UTC ii Contents Introduction 3 USDT - Userspace Statically Defined Tracepoints . .3 Portability . .3 Performance . .4 bpftrace 5 Tracing Examples 7 Listing tracepoints . .7 Simple hello world . .7 Aggregation functions . 10 Latency distributions . 11 Adding USDT support to Ruby 13 ruby-static-tracing . 13 libstapsdt . 15 Examining the dynamically loaded ELF . 16 int3 (0xCC), NOP (0x90) and uprobes . 21 USDT read arguments . 22 USDT tracing in rails 25 USDT examples in other dynamic languages 29 Ruby wrapper (featured elsewhere) . 29 Python wrapper . 29 NodeJS wrapper . 30 golang wrapper . 31 libusdt 33 kubectl-trace 35 Use in Local Development Environments 37 Using virtualization . 37 dtrace . 37 iii iv CONTENTS Listing tracepoints . 38 Simple hello world . 38 Aggregation functions . 39 Latency distributions . 39 Future Work 41 More tracers for ruby-static-tracing . 41 Kernel vs userspace buffering . 41 ustack helpers in bpftrace . 42 Ruby JIT notes . 42 BTF support . 42 USDT tracing alternatives 45 ptrace API . 45 gdb................................... 46 strace . 46 rbspy .................................... 46 rbtrace . 47 stackprof . 48 Ruby..................................... 49 Tracing api . 49 Acknowledgments 51 Works Researched . 51 Caveats 53 Unmerged patches . 53 CONTENTS 1 This document is also available in epub and pdf format if you prefer. 2 CONTENTS Introduction This document is a report on my experimentation with USDT tracing, particularly how it can be used to provide deeper insights into high-level languages like Ruby. USDT - Userspace Statically Defined Tracepoints USDT tracepoints are a powerful tool that gained popularity with dtrace. In short, USDT tracepoints allow you to build-in diagnostics at key points of an application. These can be used for debugging the application, measuring the performance characteristics, or analyzing any aspect of the runtime state of the program. USDT tracepoints are placed within your code, and are executed when: • They have been explicitly enabled. • A tracing program, such as bpftrace or dtrace is connected to it. Portability Originally limited to BSD, Solaris, and other systems with dtrace, it is now simple to use USDT tracepoints on Linux. systemtap for linux has produced sys/sdt.h that can be used to add dtrace probes to linux applications written in C/C++, and for dynamic languages libstapsdt [1] can be used to add static tracepoints using whatever C extension framework is available for the language runtime. To date, there are wrappers for golang, Python, NodeJS, and a Ruby [2] wrapper under development. bpftrace’s similarity to dtrace allows for USDT tracepoints to be accessible throughout the lifecycle of an application. While more-and-more developers use Linux, there are still a large representation of Apple laptops for professional workstations. Many such enterprises also deploy 3 4 INTRODUCTION production code to Linux systems. In such situations, developers can benefit from the insights that dtrace tracepoints have to offer them on their workstation as they are writing code. Once the code is ready to be shipped, the tracepoints can simply be left in the application. When it comes time to debug or analyze the code in production, the very same toolchain can be applied by translating dtrace’s .dt scripts into bpftrace’s ‘.bt scripts. Performance Critically, USDT tracepoints have little to no impact on performance if they are not actively being used, as it very simple to check if a static tracepoint has a probe attached to it. This makes USDT tracepoints great to deploy surgically, rather than the conven- tional “always on” diagnostics. Logging data and emitting metrics do have some runtime overhead, and it is constant. The overhead that USDT tracepoints have is minimal, and limited to when they are actively being used to help answer a question about the behavior of an application. bpftrace bpftrace [3] is an emerging new tool that is takes advantage of on eBPF support added to version 4.1 of the linux kernel. While rapidly under development, it already supports much of dtrace’s functionality and is now hit a fairly stable state with most of the important features implemented, ready more or less for production use. You can use bpftrace in production systems to attach to and summarize data from trace points similarly to with dtrace. You can run bpftrace programs by specifying a string with the -e flag, or by running a bpftrace script (conventionally ending in .bt) directly. To quickly overview how bpftrace works: • As awk treats lines, bpftrace treats probe events. You can select the type of event you want a probe to fire on, and define the probe in a stanza • bpftrace probes generate LLVM IR that is converted to eBPF instructions • The bpftrace executable reads data from eBPF maps to userspace in order to display, format, and summarize it • eBPF programs are loaded into the kernel, and fire on uprobe, kprobe, tracepoint, and other events For more details for bpftrace, check out its own reference guide [4] and this great article [5]. I started a separate report, annotating my contributions to bpftrace and explaining them, to share my insight of bpftrace internals [6]. There is an upcoming book [7] from Brendan Gregg that I covers a lot of great topics and uses of bpftrace which I highly recommend any reader pre-order, as it will certainly be the definitive book on eBPF for performance engineers. 5 6 BPFTRACE Tracing Examples For most examples, we’ll assume you have two terminals side-by-side: • One to run the program you want to trace (referred to as tracee). • One to run your bpftrace and observe the output. Note that for development cases on OS X, dtrace usage is covered elsewhere. The source and all of these scripts are available in the examples folder of this repository, or from submodules. Listing tracepoints To list tracepoints that you can trace: bpftrace -l 'usdt:*' -p ${PROCESS} Simple hello world # frozen_string_literal: true require 'ruby-static-tracing' t = StaticTracing::Tracepoint.new('global', 'hello_world', Integer, String) t.provider.enable loop do if t.enabled? t.fire(StaticTracing.nsec, 'Hello world') puts 'Probe fired!' else puts 'Not enabled' 7 8 TRACING EXAMPLES end sleep1 end This is a basic ruby script that demonstrates the basic use of static tracepoints in Ruby, using the library ruby-static-tracing [2] Ruby gem, covered later. This simplistic program will loop indefinitely, printing Not Enabled every second. This represents the Ruby program going on it’s merry way, doing what it’s supposed to be doing - pretend that it is running actual application code. The application isn’t spending any time executing probes, all it is doing is checking if the probe is enabled. Since the probe isn’t enabled, it continues with business as usual. The cost of checking if a probe is enabled is extraordinarily low, ~5 micro seconds). This example: • Creates a provider implicitly through it’s reference to ‘global’, and indicates that it will be firing off an Integer and a String to the tracepoint. • Registering the tracepoint is like a function declaration - when you fire the tracepoint later, the fire call must match the signature declared by the tracepoint. • We fetch the the provider that we created, and enable it. • Enabling the provider loads it into memory, but the tracepoint isn’t enabled until it’s attached to. Then, in an infinite loop, we check to see if our tracepoint is enabled, and fire it if it is. When we run helloworld.rb, it will loop and print: SIMPLE HELLO WORLD 9 Not enabled Not enabled Not enabled One line about every second. Not very interesting, right? When we run our tracing program though: bpftrace -e 'usdt::global:hello_nsec { printf("%lld %s\n", arg0, str(arg1))}' -p $(pgrep -f helloworld.rb) Or, using a script: bpftrace ./helloworld.bt -p $(pgrep -f helloworld.rb) helloworld.bt: usdt::global:hello_nsec { printf("%lld %s\n", arg0, str(arg1)) } We’ll notice that the output changes to indicate that the probe has been fired: Not enabled Probe fired! Probe fired! Probe fired! And, from our bpftrace process we see: Attaching 1 probe... 55369896776138 Hello world 55370897337512 Hello world 55371897691043 Hello world Upon interrupting our bpftrace with Control+C, the probe stops firing as it is no longer enabled. This demonstrates: • How to get data from ruby into our bpftrace using a tracepoint. • That probes are only enabled when they are attached to. • How to read integer and string arguments. • Basic usage of bpftrace with this gem. In subsequent examples, none of these concepts are covered again. 10 TRACING EXAMPLES Aggregation functions While the hello world sample above is powerful for debugging, it’s basically just a log statement. To do something a little more interesting, we can use an aggregation function. bpftrace can generate linear and log2 histograms on map data. Linear histograms show the same data that is used to construct an ApDex[8]. This type of tracing is good for problems like understanding request latency. For this example, we’ll use randist.rb to analyze a pseudo-random distribution of data. #!/usr/bin/env ruby require 'ruby-static-tracing' t = StaticTracing::Tracepoint.new('global', 'randist', Integer) t.provider.enable r = Random.new loop do t.fire(r.rand(100)) end The example should fire out random integers between 0 and 100. We’ll see how random it actually is with a linear histogram, bucketing the results into steps of 10: bpftrace -e 'usdt::global:randist {@ = lhist(arg0,
Recommended publications
  • Interrupt Handling in Linux
    Department Informatik Technical Reports / ISSN 2191-5008 Valentin Rothberg Interrupt Handling in Linux Technical Report CS-2015-07 November 2015 Please cite as: Valentin Rothberg, “Interrupt Handling in Linux,” Friedrich-Alexander-Universitat¨ Erlangen-Nurnberg,¨ Dept. of Computer Science, Technical Reports, CS-2015-07, November 2015. Friedrich-Alexander-Universitat¨ Erlangen-Nurnberg¨ Department Informatik Martensstr. 3 · 91058 Erlangen · Germany www.cs.fau.de Interrupt Handling in Linux Valentin Rothberg Distributed Systems and Operating Systems Dept. of Computer Science, University of Erlangen, Germany [email protected] November 8, 2015 An interrupt is an event that alters the sequence of instructions executed by a processor and requires immediate attention. When the processor receives an interrupt signal, it may temporarily switch control to an inter- rupt service routine (ISR) and the suspended process (i.e., the previously running program) will be resumed as soon as the interrupt is being served. The generic term interrupt is oftentimes used synonymously for two terms, interrupts and exceptions [2]. An exception is a synchronous event that occurs when the processor detects an error condition while executing an instruction. Such an error condition may be a devision by zero, a page fault, a protection violation, etc. An interrupt, on the other hand, is an asynchronous event that occurs at random times during execution of a pro- gram in response to a signal from hardware. A proper and timely handling of interrupts is critical to the performance, but also to the security of a computer system. In general, interrupts can be emitted by hardware as well as by software. Software interrupts (e.g., via the INT n instruction of the x86 instruction set architecture (ISA) [5]) are means to change the execution context of a program to a more privileged interrupt context in order to enter the kernel and, in contrast to hardware interrupts, occur synchronously to the currently running program.
    [Show full text]
  • User Manual Issue 2.0.2 September 2017
    The Embedded I/O Company TDRV015-SW-82 Linux Device Driver Reconfigurable FPGA Version 2.0.x User Manual Issue 2.0.2 September 2017 TEWS TECHNOLOGIES GmbH Am Bahnhof 7 25469 Halstenbek, Germany Phone: +49 (0) 4101 4058 0 Fax: +49 (0) 4101 4058 19 e-mail: [email protected] www.tews.com TDRV015-SW-82 This document contains information, which is Linux Device Driver proprietary to TEWS TECHNOLOGIES GmbH. Any Reconfigurable FPGA reproduction without written permission is forbidden. Supported Modules: TEWS TECHNOLOGIES GmbH has made any TAMC631 (TPLD001) effort to ensure that this manual is accurate and TAMC640 (TPLD002) complete. However TEWS TECHNOLOGIES GmbH TAMC641 (TPLD003) reserves the right to change the product described TAMC651 (TPLD004) in this document at any time without notice. TPMC632 (TPLD005) TEWS TECHNOLOGIES GmbH is not liable for any damage arising out of the application or use of the device described herein. 2011-2017 by TEWS TECHNOLOGIES GmbH Issue Description Date 1.0.0 First Issue March 14, 2011 1.0.1 SupportedModulesadded September30,2011 2.0.0 New API implemented March 7, 2012 2.0.1 IncludestatementinExampleCodescorrected August 18, 2015 Reference to Engineering Documentation removed 2.0.2 Filelistmodified(licenseadded) September28,2017 TDRV015-SW-82 - Linux Device Driver Page 2 of 75 Table of Contents 1 INTRODUCTION......................................................................................................... 4 2 INSTALLATION.........................................................................................................
    [Show full text]
  • Faux Disk Encryption: Realities of Secure Storage on Mobile Devices August 4, 2015 – Version 1.0
    NCC Group Whitepaper Faux Disk Encryption: Realities of Secure Storage On Mobile Devices August 4, 2015 – Version 1.0 Prepared by Daniel A. Mayer — Principal Security Consultant Drew Suarez — Senior Security Consultant Abstract In this paper, we discuss the challenges mobile app developers face in securing data stored on devices including mobility, accessibility, and usability requirements. Given these challenges, we first debunk common misconceptions about full-disk encryption and show why it is not sufficient for many attack scenarios. We then systematically introduce the more sophisticated secure storage techniques that are available for iOS and Android respectively. For each platform, we discuss in-depth which mechanisms are available, how they technically operate, and whether they fulfill the practical security and usability requirements. We conclude the paper with an analysis of what still can go wrong even when current best-practices are followed and what the security and mobile device community can do to address these shortcomings. Table of Contents 1 Introduction ......................................................................... 3 2 Challenges in Secure Mobile Storage .................................................. 4 3 Threat Model Considerations ......................................................... 5 4 Secure Data Storage on iOS .......................................................... 6 4.1 Fundamentals of iOS Data Protection .................................................. 7 4.2 Filesystem Encryption ..............................................................
    [Show full text]
  • Linux Kernel and Driver Development Training Slides
    Linux Kernel and Driver Development Training Linux Kernel and Driver Development Training © Copyright 2004-2021, Bootlin. Creative Commons BY-SA 3.0 license. Latest update: October 9, 2021. Document updates and sources: https://bootlin.com/doc/training/linux-kernel Corrections, suggestions, contributions and translations are welcome! embedded Linux and kernel engineering Send them to [email protected] - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 1/470 Rights to copy © Copyright 2004-2021, Bootlin License: Creative Commons Attribution - Share Alike 3.0 https://creativecommons.org/licenses/by-sa/3.0/legalcode You are free: I to copy, distribute, display, and perform the work I to make derivative works I to make commercial use of the work Under the following conditions: I Attribution. You must give the original author credit. I Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. I For any reuse or distribution, you must make clear to others the license terms of this work. I Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. Document sources: https://github.com/bootlin/training-materials/ - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 2/470 Hyperlinks in the document There are many hyperlinks in the document I Regular hyperlinks: https://kernel.org/ I Kernel documentation links: dev-tools/kasan I Links to kernel source files and directories: drivers/input/ include/linux/fb.h I Links to the declarations, definitions and instances of kernel symbols (functions, types, data, structures): platform_get_irq() GFP_KERNEL struct file_operations - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 3/470 Company at a glance I Engineering company created in 2004, named ”Free Electrons” until Feb.
    [Show full text]
  • Linux Kernal II 9.1 Architecture
    Page 1 of 7 Linux Kernal II 9.1 Architecture: The Linux kernel is a Unix-like operating system kernel used by a variety of operating systems based on it, which are usually in the form of Linux distributions. The Linux kernel is a prominent example of free and open source software. Programming language The Linux kernel is written in the version of the C programming language supported by GCC (which has introduced a number of extensions and changes to standard C), together with a number of short sections of code written in the assembly language (in GCC's "AT&T-style" syntax) of the target architecture. Because of the extensions to C it supports, GCC was for a long time the only compiler capable of correctly building the Linux kernel. Compiler compatibility GCC is the default compiler for the Linux kernel source. In 2004, Intel claimed to have modified the kernel so that its C compiler also was capable of compiling it. There was another such reported success in 2009 with a modified 2.6.22 version of the kernel. Since 2010, effort has been underway to build the Linux kernel with Clang, an alternative compiler for the C language; as of 12 April 2014, the official kernel could almost be compiled by Clang. The project dedicated to this effort is named LLVMLinxu after the LLVM compiler infrastructure upon which Clang is built. LLVMLinux does not aim to fork either the Linux kernel or the LLVM, therefore it is a meta-project composed of patches that are eventually submitted to the upstream projects.
    [Show full text]
  • Singularityce User Guide Release 3.8
    SingularityCE User Guide Release 3.8 SingularityCE Project Contributors Aug 16, 2021 CONTENTS 1 Getting Started & Background Information3 1.1 Introduction to SingularityCE......................................3 1.2 Quick Start................................................5 1.3 Security in SingularityCE........................................ 15 2 Building Containers 19 2.1 Build a Container............................................. 19 2.2 Definition Files.............................................. 24 2.3 Build Environment............................................ 35 2.4 Support for Docker and OCI....................................... 39 2.5 Fakeroot feature............................................. 79 3 Signing & Encryption 83 3.1 Signing and Verifying Containers.................................... 83 3.2 Key commands.............................................. 88 3.3 Encrypted Containers.......................................... 90 4 Sharing & Online Services 95 4.1 Remote Endpoints............................................ 95 4.2 Cloud Library.............................................. 103 5 Advanced Usage 109 5.1 Bind Paths and Mounts.......................................... 109 5.2 Persistent Overlays............................................ 115 5.3 Running Services............................................. 118 5.4 Environment and Metadata........................................ 129 5.5 OCI Runtime Support.......................................... 140 5.6 Plugins.................................................
    [Show full text]
  • Linux GPIO: Evolution and Current State of the User
    Linux GPIO: Evolution and Current State of the User API Embedded Linux Conference 2020 Bartosz Golaszewski About us ● Embedded Linux Engineering Firm ● ~40 senior engineers, coming from the semiconductor world ● HW and SW products: from concept to manufacturing ● Upstream Linux kernel development and maintenance ● Founding developers of kernelCI.org project About me ● 10 years experience ● Kernel and user-space developer ● Maintainer of libgpiod and co-maintainer of the GPIO kernel sub-system 2 A lot can change in a couple months... 3 A lot can change in a couple months... The GPIO character device has been extended with new features in linux v5.5 and final new additions before declaring it feature-complete are planned for v5.6 & v5.7. 4 A lot can change in a couple months... The GPIO character device has been extended with new features in linux v5.5 but due to shortcomings in the first version of the ABI, the existing ioctl() calls are being retired and v2 of the ABI is being introduced aiming at a release as part of linux v5.9. 5 Linux GPIO: A Lesson in user API design Embedded Linux Conference 2020 Bartosz Golaszewski Agenda 1. Current state of user API a. sysfs = bad b. Character device c. Recently added features d. GPIO aggregator 2. Upcoming overhaul a. What’s wrong? b. What’s new? c. Advice on designing good uAPI 3. libgpiod a. what’s new b. Future 7 Current state of GPIO uAPI 8 GPIO in userspace ● Writing drivers for devices using GPIOs is encouraged wherever possible, but..
    [Show full text]
  • Fabric Manager for NVIDIA Nvswitch Systems
    Fabric Manager for NVIDIA NVSwitch Systems User Guide / Virtualization / High Availability Modes DU-09883-001_v0.7 | January 2021 Document History DU-09883-001_v0.7 Version Date Authors Description of Change 0.1 Oct 25, 2019 SB Initial Beta Release 0.2 Mar 23, 2020 SB Updated error handling and bare metal mode 0.3 May 11, 2020 YL Updated Shared NVSwitch APIs section with new API information 0.4 July 7, 2020 SB Updated MIG interoperability and high availability details. 0.5 July 17, 2020 SB Updated running as non-root instructions 0.6 Aug 03, 2020 SB Updated installation instructions based on CUDA repo and updated SXid error details 0.7 Jan 26, 2021 GT, CC Updated with vGPU multitenancy virtualization mode Fabric Ma nager fo r NVI DIA NVSwitch Sy stems DU-09883-001_v0.7 | ii Table of Contents Chapter 1. Overview ...................................................................................................... 1 1.1 Introduction .............................................................................................................1 1.2 Terminology ............................................................................................................1 1.3 NVSwitch Core Software Stack .................................................................................2 1.4 What is Fabric Manager?..........................................................................................3 Chapter 2. Getting Started With Fabric Manager ...................................................... 5 2.1 Basic Components...................................................................................................5
    [Show full text]
  • Documentation and Analysis of the Linux Random Number Generator
    Documentation and Analysis of the Linux Random Number Generator Version: 3.6 Document history Version Date Editor Description 2.0 2018-03-21 Stephan Müller Covering kernel 4.15 Re-running all tests of chapters 6 and following on 4.15 2.1 2018-04-11 Stephan Müller Updating the test results for the reboot tests on bare metal with 50,000 reboot cycles 2.2 2018-04-11 Stephan Müller Covering kernel 4.16 2.3 2018-06-18 Stephan Müller Covering kernel 4.17 2.4 2018-08-24 Stephan Müller Covering kernel 4.18 2.5 2018-11-12 Stephan Müller Covering kernel 4.19 Updated seeding process ChaCha20 DRNG documented 2.6 2019-01-11 Stephan Müller Covering kernel 4.20 3.0 2019-04-05 Stephan Müller Covering kernel 5.0 Re-running all tests of chapters 6 and following on 5.0 3.1 2019-04-12 Stephan Müller Adding results of reboot-tests for 5.0 3.2 2019-05-17 Stephan Müller Addressing comments from BSI Covering kernel 5.1 3.3 2019-08-13 Stephan Müller Covering kernel 5.2 3.4 2019-09-26 Stephan Müller Covering kernel 5.3 3.5 2019-12-13 Stephan Müller Covering kernel 5.4 3.6 2020-04-07 Stephan Müller Covering kernel 5.5 Federal Office for Information Security Post Box 20 03 63 D-53133 Bonn Internet: https://www.bsi.bund.de © Federal Office for Information Security 2020 Document history This analysis was prepared for BSI by atsec information security GmbH.
    [Show full text]
  • (Thingspro Gateway V2.6.0 Installation File for Debian 9) Release Notes
    Software Package for ThingsPro 2 (ThingsPro Gateway v2.6.0 installation file for Debian 9) Release Notes Version: v2.6.0 Build: Build 20200616 Release Date: Jul 31, 2020 Applicable Products MC-1121-E2-T, MC-1121-E4-T, MC-1121-E4-T-US, UC-2100 Series, UC-2100-W Series, UC-3100 Series, UC-5100 Series, UC-8112-LX, UC-8112-ME-T-LX, UC-8112-ME-T-LX1, UC-8100A-ME-T Series, UC-8200 Series Supported Operating Systems Moxa Industrial Linux (Debian 9) New Features • Core: ThingsPro now supports Python 3 (Python 2 is deprecated). • Modbus: Shows Modbus TX/RX packet in debug mode. • AWS IoT Core: Supports 0 and 1 settings in QoS. • Aliyun IoT Platform: Supports 0 and 1 settings in QoS. • Sparkplug: Support user-scheduled periodic group uploading of tags. Enhancements • Modbus: Improved the TCP/RTU reconnect mechanism. • Modbus: Serial port will not be occupied if no RTU device is configured. Bugs Fixed • Cellular: An incorrect tag name. • Cellular: Apply the watchdog to prevent system freeze during the reboot process. • Cellular: Keepalive fails due to arping bind with the MAC address of the host instead of the target. • Route: The routing priority is not working when the cellular interface is not WWAN0. • Route: Changing route priority frequently could lead to a deadlock. • OpenVPN: Missing DNS information when OpenVPN is enabled or disabled. • OpenVPN: DNS info missing in the default route update script. • OpenVPN: Incorrect status for MC1121. • AVEVA Insight: All datatypes are changed to string value type in JSON payload. Keep the original datatype.
    [Show full text]
  • Designing a Fast Index Format for Git
    Free University of Bolzano - Bozen Bachelor Thesis Designing a Fast Index Format for Git Author: Supervisor: Thomas Gummerer Dr. Johann Gamper A thesis submitted in fulfillment of the requirements for the degree of Bachelor in Computer Science in July 2013 Contents List of Figures iv Abstract v 1 Introduction1 1.1 Motivation...................................1 1.2 Problem Description and Objectives.....................2 1.3 Organization of the Thesis...........................2 2 Related Work4 2.1 Version Control Systems............................4 2.2 Types of Version Control Systems.......................4 2.3 Git........................................5 3 A New Index for Git7 3.1 The Git Index File...............................7 3.2 Index v2.....................................8 3.3 The New Index File Format v5........................ 11 4 Implementation 15 4.1 Convert Index.................................. 15 4.2 Read Index................................... 15 4.3 Internal Implementation............................ 16 4.4 New In-memory Format............................ 18 4.5 Index Reading API............................... 19 4.6 Writing the New Index Format........................ 20 5 Discussion 22 5.1 Alternative Solutions.............................. 22 5.1.1 B-tree Format............................. 22 5.1.2 Append-only Data Structure..................... 22 5.1.3 Database Format............................ 23 5.1.4 Padded Structure............................ 23 5.2 Discussion.................................... 24 6
    [Show full text]
  • A Technical Companion to Windows Embedded Automotive 7 Proven Technology Adapted for the Automotive Industry
    A Technical Companion to Windows Embedded Automotive 7 Proven technology adapted for the automotive industry Published: July 2010 For the latest information, please see: www.windowsembedded.com/auto Abstract Windows® Embedded Automotive 7―based on the newest generation of embedded operating systems from Microsoft and combining the award-winning Windows® Automotive and Microsoft® Auto platforms―is designed specifically for developing state-of-the-art, in-vehicle infotainment systems. It offers a standardized, industry-proven platform for building communication, entertainment, and service-enabled location-based solutions. This release of Windows Embedded Automotive includes a large set of integrated, tested, and flexible middleware components and tools, in addition to hundreds of components that are available with Windows® Embedded Compact 7. These components make it possible for Windows Embedded Automotive 7–based systems to scale across a broad range of automotive makes and models. By capitalizing on these tools and on the broad Microsoft partner ecosystem, suppliers can reduce development costs and speed time-to-market while extending customers’ lifestyles into the vehicles that they drive. Table of Contents TABLE OF FIGURES ................................................................................................................................... 4 OVERVIEW ............................................................................................................................................... 5 THE BUSINESS CASE FOR WINDOWS
    [Show full text]