DOCSLIB.ORG

What´S up in Kernel-Land?

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
What´S up in Kernel-Land? What´s up in Kernel-Land? 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 1 Target audience? Users of these! ...and many more Linux-Distributions for Laptops, Desktops and Servers 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 2 whoami @ work Kernel-Log 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 3 whoami @ home 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 4 Micro-Blogging ● @thleemhuis private/personal stuff German ● @knurd666 Fedora related things English ● @kernellogauthor Kernel-Log topics English ● @kernellog announces new Kernel Logs on heise.de German ● @kernellog2 announces new Kernel Logs on h-online.com English 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 5 The next 35 minutes ● quick overview: Linux development model, stable series ● main part: the different areas of the kernel – what got improved recently – what people are working on ● how to help ● summing up + questions ● there are a lot of more topics I can talk about if you want – but I doubt there will be much free time remaining, as the main part is packed with details already 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 6 "Use bullet points rarely" ● you ● won't ● see ● many ● bullet ● points ● in ● this ● presentation 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 7 "Use bullet points rarely" ● you ● won't ● see ● many ● bullet ● points ● in ● this ● presentation If you really think you need something to read, then open you laptop and look at the notes of this presentation: http://bit.ly/lk2010-kernellog 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 8 Constant development within 2.6 2.6.26 2.6.27 2.6.28 2.6.29 2.6.30 2.6.31 (14.07.2007) (10.10.2008) (24.12.2008) (24.03.2009) (10.06.2009) (10.09.2009) 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 9 Merge window 2.6.26 2.6.27 2.6.28 2.6.29 2.6.30 2.6.31 (14.07.2007) (10.10.2008) (24.12.2008) (24.03.2009) (10.06.2009) (10.09.2009) 2.6.31 2.6.30 -rc1 Merge Window 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 10 Stabilization phase 2.6.26 2.6.27 2.6.28 2.6.29 2.6.30 2.6.31 (14.07.2007) (10.10.2008) (24.12.2008) (24.03.2009) (10.06.2009) (10.09.2009) 2.6.31 2.6.31 2.6.31 2.6.31 2.6.26 2.6.30 -rc1 -rc2 -rc3 -rc4 -rc n 2.6.31 Merge Window stabilization phase 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 11 Growth 13500000 13000000 12500000 12000000 e d o c 11500000 l l e u 11000000 Q n e l i 10500000 e Z 10000000 9500000 9000000 2.6.28 2.6.30 2.6.32 2.6.27 2.6.29 2.6.31 2.6.33 Kernel-Version 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 12 Growth 13500000 13000000 12500000 12000000 late merge e d of a SCSI FC o c 11500000 driver l l e u 11000000 Q n e RC1 l i 10500000 e Z 10000000 9500000 9000000 2.6.28 2.6.30 2.6.32 2.6.27 2.6.29 2.6.31 2.6.33 Kernel-Version 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 13 Some stats 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 14 Stable series 2.6.29 2.6.30 (24.03.09) -rc n 2.6.29.1 (02.04.) 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 15 Stable series 2.6.29 2.6.30 2.6.30 2.6.31 2.6.31 (24.03.09) -rc n (10.06.09) -rc n (10.09.09) 2.6.31.1 (24.09.) 2.6.30.1 2.6.30.10 ... (03.07.) (04.12.) 2.6.29.1 2.6.29.4 2.6.29.5 2.6.29.6 ... (02.04.) (20.05.) (15.06.) (03.07.) 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 16 Stable series 2.6.29 2.6.30 2.6.30 2.6.31 2.6.31 (24.03.09) -rc n (10.06.09) -rc n (10.09.09) 2.6.31.1 (24.09.) 2.6.30.1 2.6.30.10 ... (03.07) (04.12) EOL: after 3 months 2.6.29.1 2.6.29.4 2.6.29.5 2.6.29.6 ... EOL: after six months (02.04.) (20.05.) (15.06.) (03.07.) 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 17 Stable series 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 18 Stable series: status ● 2.4.xx: not yet dead, but dying ● 2.6.27: growing old: will soon be dropped or frozen deeper ● 2.6.32: current "long term stable release" ● 2.6.34: support stopped recently ● 2.6.35: current 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 19 Where we are, where we head 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 20 Graphics hardware: AMD/ATI 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 21 Graphics hardware: Intel 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 22 Graphics hardware: Nvidia 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 23 09/24/10 Graphics hardware: Various hardware: Graphics YouTube: PDds73yDCNo ThorstenLeemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 http://bit.ly/lk2010-kernellog– 24 Network 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 25 Side note: staging 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 26 Storage 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 27 Storage 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 28 File systems 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 29 File systems 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 30 Architecture 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 31 Virtualization 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 32 Security 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 33 Tracing/Debugging 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 34 Memory management (MM) 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 35 Power management (PM) 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 36 Various: drivers 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 37 Various: infrastructure 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 38 Various: userspace 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 39 09/24/10 Staying up2date: Kernel-Log (de) Kernel-Log up2date: Staying http://www.heise.de/open/ ThorstenLeemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 http://bit.ly/lk2010-kernellog– 40 09/24/10 Staying up2date: Kernel-Log (en) Kernel-Log up2date: Staying http://www.h-online.com/open/ ThorstenLeemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 http://bit.ly/lk2010-kernellog– 41 09/24/10 Staying up2date: Linux Weekly News Linux Weekly up2date: Staying http://lwn.net/ ThorstenLeemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 http://bit.ly/lk2010-kernellog– 42 09/24/10 Staying up2date: Weather Forecast Weather up2date: Staying http://www.linuxfoundation.org/collaborate/lwf ThorstenLeemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 http://bit.ly/lk2010-kernellog– 43 09/24/10 Staying up2date: Kernelnewbies up2date: Staying http://kernelnewbies.org/LinuxChanges ThorstenLeemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 http://bit.ly/lk2010-kernellog– 44 09/24/10 Test and Report bugs! Report and Test http://bugzilla.kernel.org/ ThorstenLeemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 http://bit.ly/lk2010-kernellog– 45 09/24/10 Test -rc -rc Kernels! Test http://bit.ly/tytso-help-testing ThorstenLeemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 http://bit.ly/lk2010-kernellog– 46 Regression Reports 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 47 Finally () ● 2.6.35 (released in August) – RPS, RFS, memory compaction, direct I/O for Btrfs, Kdb, perf ● 2.6.36 in mid October – AppArmor, fanotify, Concurrency-managed workqueues, new OOM, latency reduction, CIFS FS-Cache – improved hardware support thanks to new and improved drivers ● 2.6.37 for the start of next year ● still a lot happening, as there still is a lot to do – but yes, maybe things are slowing down a bit ● support for 2.6.27 might soon stop (and 2.4 as well) ● always upgrade to the latest stable releases – or use a kernel from a distribution to let the distributor fix all security bugs for you 09/24/10 Thorsten Leemhuis aka thl aka @kernellogauthor Kernel-Log live – LK2010 – http://bit.ly/lk2010-kernellog 48 Wanna know more about these? Ask! ● LWN: Who writes the kernel – Hobby vs.
Load more

Recommended publications
  • Shorten Device Boot Time for Automotive IVI and Navigation Systems
    Shorten Device Boot Time for Automotive IVI and Navigation Systems Jim Huang ( 黃敬群 ) <[email protected]> Dr. Shi-wu Lo <[email protected]> May 28, 2013 / Automotive Linux Summit (Spring) Rights to copy © Copyright 2013 0xlab http://0xlab.org/ [email protected] Attribution – ShareAlike 3.0 Corrections, suggestions, contributions and translations You are free are welcome! to copy, distribute, display, and perform the work to make derivative works Latest update: May 28, 2013 to make commercial use of the work Under the following conditions Attribution. You must give the original author credit. 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. For any reuse or distribution, you must make clear to others the license terms of this work. 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. License text: http://creativecommons.org/licenses/by-sa/3.0/legalcode Goal of This Presentation • Propose a practical approach of the mixture of ARM hibernation (suspend to disk) and Linux user-space checkpointing – to shorten device boot time • An intrusive technique for Android/Linux – minimal init script and root file system changes are required • Boot time is one of the key factors for Automotive IVI – mentioned by “Linux Powered Clusters” and “Silver Bullet of Virtualization (Pitfalls, Challenges and Concerns) Continued” at ALS 2013 – highlighted by “Boot Time Optimizations” at ALS 2012 About this presentation • joint development efforts of the following entities – 0xlab team - http://0xlab.org/ – OSLab, National Chung Cheng University of Taiwan, led by Dr.
    [Show full text]
  • Development of a Verified Flash File System ⋆
    Development of a Verified Flash File System ? Gerhard Schellhorn, Gidon Ernst, J¨orgPf¨ahler,Dominik Haneberg, and Wolfgang Reif Institute for Software & Systems Engineering University of Augsburg, Germany fschellhorn,ernst,joerg.pfaehler,haneberg,reifg @informatik.uni-augsburg.de Abstract. This paper gives an overview over the development of a for- mally verified file system for flash memory. We describe our approach that is based on Abstract State Machines and incremental modular re- finement. Some of the important intermediate levels and the features they introduce are given. We report on the verification challenges addressed so far, and point to open problems and future work. We furthermore draw preliminary conclusions on the methodology and the required tool support. 1 Introduction Flaws in the design and implementation of file systems already lead to serious problems in mission-critical systems. A prominent example is the Mars Explo- ration Rover Spirit [34] that got stuck in a reset cycle. In 2013, the Mars Rover Curiosity also had a bug in its file system implementation, that triggered an au- tomatic switch to safe mode. The first incident prompted a proposal to formally verify a file system for flash memory [24,18] as a pilot project for Hoare's Grand Challenge [22]. We are developing a verified flash file system (FFS). This paper reports on our progress and discusses some of the aspects of the project. We describe parts of the design, the formal models, and proofs, pointing out challenges and solutions. The main characteristic of flash memory that guides the design is that data cannot be overwritten in place, instead space can only be reused by erasing whole blocks.
    [Show full text]
  • Linux on the Road
    Linux on the Road Linux with Laptops, Notebooks, PDAs, Mobile Phones and Other Portable Devices Werner Heuser <wehe[AT]tuxmobil.org> Linux Mobile Edition Edition Version 3.22 TuxMobil Berlin Copyright © 2000-2011 Werner Heuser 2011-12-12 Revision History Revision 3.22 2011-12-12 Revised by: wh The address of the opensuse-mobile mailing list has been added, a section power management for graphics cards has been added, a short description of Intel's LinuxPowerTop project has been added, all references to Suspend2 have been changed to TuxOnIce, links to OpenSync and Funambol syncronization packages have been added, some notes about SSDs have been added, many URLs have been checked and some minor improvements have been made. Revision 3.21 2005-11-14 Revised by: wh Some more typos have been fixed. Revision 3.20 2005-11-14 Revised by: wh Some typos have been fixed. Revision 3.19 2005-11-14 Revised by: wh A link to keytouch has been added, minor changes have been made. Revision 3.18 2005-10-10 Revised by: wh Some URLs have been updated, spelling has been corrected, minor changes have been made. Revision 3.17.1 2005-09-28 Revised by: sh A technical and a language review have been performed by Sebastian Henschel. Numerous bugs have been fixed and many URLs have been updated. Revision 3.17 2005-08-28 Revised by: wh Some more tools added to external monitor/projector section, link to Zaurus Development with Damn Small Linux added to cross-compile section, some additions about acoustic management for hard disks added, references to X.org added to X11 sections, link to laptop-mode-tools added, some URLs updated, spelling cleaned, minor changes.
    [Show full text]
  • Kernel Boot-Time Tracing
    Kernel Boot-time Tracing Linux Plumbers Conference 2019 - Tracing Track Masami Hiramatsu <[email protected]> Linaro, Ltd. Speaker Masami Hiramatsu - Working for Linaro and Linaro members - Tech Lead for a Landing team - Maintainer of Kprobes and related tracing features/tools Why Kernel Boot-time Tracing? Debug and analyze boot time errors and performance issues - Measure performance statistics of kernel boot - Analyze driver init failure - Debug boot up process - Continuously tracing from boot time etc. What We Have There are already many ftrace options on kernel command line ● Setup options (trace_options=) ● Output to printk (tp_printk) ● Enable events (trace_events=) ● Enable tracers (ftrace=) ● Filtering (ftrace_filter=,ftrace_notrace=,ftrace_graph_filter=,ftrace_graph_notrace=) ● Add kprobe events (kprobe_events=) ● And other options (alloc_snapshot, traceoff_on_warning, ...) See Documentation/admin-guide/kernel-parameters.txt Example of Kernel Cmdline Parameters In grub.conf linux /boot/vmlinuz-5.1 root=UUID=5a026bbb-6a58-4c23-9814-5b1c99b82338 ro quiet splash tp_printk trace_options=”sym-addr” trace_clock=global ftrace_dump_on_oops trace_buf_size=1M trace_event=”initcall:*,irq:*,exceptions:*” kprobe_event=”p:kprobes/myevent foofunction $arg1 $arg2;p:kprobes/myevent2 barfunction %ax” What Issues? Size limitation ● kernel cmdline size is small (< 256bytes) ● A half of the cmdline is used for normal boot Only partial features supported ● ftrace has too complex features for single command line ● per-event filters/actions, instances, histograms. Solutions? 1. Use initramfs - Too late for kernel boot time tracing 2. Expand kernel cmdline - It is not easy to write down complex tracing options on bootloader (Single line options is too simple) 3. Reuse structured boot time data (Devicetree) - Well documented, structured data -> V1 & V2 series based on this. Boot-time Trace: V1 and V2 series V1 and V2 series posted at June.
    [Show full text]
  • ZBD: Using Transparent Compression at the Block Level to Increase Storage Space Efficiency
    ZBD: Using Transparent Compression at the Block Level to Increase Storage Space Efficiency Thanos Makatos∗†, Yannis Klonatos∗†, Manolis Marazakis∗, Michail D. Flouris∗, and Angelos Bilas∗† ∗ Foundation for Research and Technology - Hellas (FORTH) Institute of Computer Science (ICS) 100 N. Plastira Av., Vassilika Vouton, Heraklion, GR-70013, Greece † Department of Computer Science, University of Crete P.O. Box 2208, Heraklion, GR 71409, Greece {mcatos, klonatos, maraz, flouris, bilas}@ics.forth.gr Abstract—In this work we examine how transparent compres- • Logical to physical block mapping: Block-level compres- sion in the I/O path can improve space efficiency for online sion imposes a many-to-one mapping from logical to storage. We extend the block layer with the ability to compress physical blocks, as multiple compressed logical blocks and decompress data as they flow between the file-system and the disk. Achieving transparent compression requires extensive must be stored in the same physical block. This requires metadata management for dealing with variable block sizes, dy- using a translation mechanism that imposes low overhead namic block mapping, block allocation, explicit work scheduling in the common I/O path and scales with the capacity and I/O optimizations to mitigate the impact of additional I/Os of the underlying devices as well as a block alloca- and compression overheads. Preliminary results show that online tion/deallocation mechanism that affects data placement. transparent compression is a viable option for improving effective • storage capacity, it can improve I/O performance by reducing Increased number of I/Os: Using compression increases I/O traffic and seek distance, and has a negative impact on the number of I/Os required on the critical path during performance only when single-thread I/O latency is critical.
    [Show full text]
  • Hiding Process Memory Via Anti-Forensic Techniques
    DIGITAL FORENSIC RESEARCH CONFERENCE Hiding Process Memory via Anti-Forensic Techniques By: Frank Block (Friedrich-Alexander Universität Erlangen-Nürnberg (FAU) and ERNW Research GmbH) and Ralph Palutke (Friedrich-Alexander Universität Erlangen-Nürnberg) From the proceedings of The Digital Forensic Research Conference DFRWS USA 2020 July 20 - 24, 2020 DFRWS is dedicated to the sharing of knowledge and ideas about digital forensics research. Ever since it organized the first open workshop devoted to digital forensics in 2001, DFRWS continues to bring academics and practitioners together in an informal environment. As a non-profit, volunteer organization, DFRWS sponsors technical working groups, annual conferences and challenges to help drive the direction of research and development. https://dfrws.org Forensic Science International: Digital Investigation 33 (2020) 301012 Contents lists available at ScienceDirect Forensic Science International: Digital Investigation journal homepage: www.elsevier.com/locate/fsidi DFRWS 2020 USA d Proceedings of the Twentieth Annual DFRWS USA Hiding Process Memory Via Anti-Forensic Techniques Ralph Palutke a, **, 1, Frank Block a, b, *, 1, Patrick Reichenberger a, Dominik Stripeika a a Friedrich-Alexander Universitat€ Erlangen-Nürnberg (FAU), Germany b ERNW Research GmbH, Heidelberg, Germany article info abstract Article history: Nowadays, security practitioners typically use memory acquisition or live forensics to detect and analyze sophisticated malware samples. Subsequently, malware authors began to incorporate anti-forensic techniques that subvert the analysis process by hiding malicious memory areas. Those techniques Keywords: typically modify characteristics, such as access permissions, or place malicious data near legitimate one, Memory subversion in order to prevent the memory from being identified by analysis tools while still remaining accessible.
    [Show full text]
  • The Best of Both Worlds with On-Demand Virtualization
    The Best of Both Worlds with On-Demand Virtualization Thawan Kooburat, Michael Swift University of Wisconsin-Madison [email protected], [email protected] Abstract Virtualization offers many benefits such as live migration, resource consolidation, and checkpointing. However, there are many cases where the overhead of virtualization is too high to justify for its merits. Most desktop and laptop PCs and many large web properties run natively because the benefits of virtualization are too small compared to the overhead. We propose a new middle ground: on-demand virtualization, in which systems run natively when they need native performance or features but can be converted on-the-fly to run virtually when necessary. This enables the user or system administrator to leverage the most useful features of virtualization, such as or checkpointing or consolidating workloads, during off-peak hours without paying the overhead during peak usage. We have developed a prototype of on-demand virtualization in Linux using the hibernate feature to transfer state between native execution and virtual execution, and find even networking applications can survive being virtualized. OS can return to native execution on its original hardware. 1. Introduction We call this approach on-demand virtualization, and it System virtualization offers many benefits in both data- gives operating systems an ability to be virtualized center and desktop environments, such as live migration, without service disruption. multi-tenancy, checkpointing, and the ability to run dif- Reaping the benefits of virtualization without its costs ferent operating systems at once. These features enable has been proposed previously in other forms. Microvisors hardware maintenance with little downtime, load ba- [14] provided the first step in the direction toward lancing for better throughput or power efficiency, and on-demand virtualization.
    [Show full text]
  • Demystifying Internet of Things Security Successful Iot Device/Edge and Platform Security Deployment — Sunil Cheruvu Anil Kumar Ned Smith David M
    Demystifying Internet of Things Security Successful IoT Device/Edge and Platform Security Deployment — Sunil Cheruvu Anil Kumar Ned Smith David M. Wheeler Demystifying Internet of Things Security Successful IoT Device/Edge and Platform Security Deployment Sunil Cheruvu Anil Kumar Ned Smith David M. Wheeler Demystifying Internet of Things Security: Successful IoT Device/Edge and Platform Security Deployment Sunil Cheruvu Anil Kumar Chandler, AZ, USA Chandler, AZ, USA Ned Smith David M. Wheeler Beaverton, OR, USA Gilbert, AZ, USA ISBN-13 (pbk): 978-1-4842-2895-1 ISBN-13 (electronic): 978-1-4842-2896-8 https://doi.org/10.1007/978-1-4842-2896-8 Copyright © 2020 by The Editor(s) (if applicable) and The Author(s) This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. Open Access This book is licensed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license and indicate if changes were made. The images or other third party material in this book are included in the book’s Creative Commons license, unless indicated otherwise in a credit line to the material.
    [Show full text]
  • Improving the Performance of Hybrid Main Memory Through System Aware Management of Heterogeneous Resources
    IMPROVING THE PERFORMANCE OF HYBRID MAIN MEMORY THROUGH SYSTEM AWARE MANAGEMENT OF HETEROGENEOUS RESOURCES by Juyoung Jung B.S. in Information Engineering, Korea University, 2000 Master in Computer Science, University of Pittsburgh, 2013 Submitted to the Graduate Faculty of the Kenneth P. Dietrich School of Arts and Sciences in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Computer Science University of Pittsburgh 2016 UNIVERSITY OF PITTSBURGH KENNETH P. DIETRICH SCHOOL OF ARTS AND SCIENCES This dissertation was presented by Juyoung Jung It was defended on December 7, 2016 and approved by Rami Melhem, Ph.D., Professor at Department of Computer Science Bruce Childers, Ph.D., Professor at Department of Computer Science Daniel Mosse, Ph.D., Professor at Department of Computer Science Jun Yang, Ph.D., Associate Professor at Electrical and Computer Engineering Dissertation Director: Rami Melhem, Ph.D., Professor at Department of Computer Science ii IMPROVING THE PERFORMANCE OF HYBRID MAIN MEMORY THROUGH SYSTEM AWARE MANAGEMENT OF HETEROGENEOUS RESOURCES Juyoung Jung, PhD University of Pittsburgh, 2016 Modern computer systems feature memory hierarchies which typically include DRAM as the main memory and HDD as the secondary storage. DRAM and HDD have been extensively used for the past several decades because of their high performance and low cost per bit at their level of hierarchy. Unfortunately, DRAM is facing serious scaling and power consumption problems, while HDD has suffered from stagnant performance improvement and poor energy efficiency. After all, computer system architects have an implicit consensus that there is no hope to improve future system’s performance and power consumption unless something fundamentally changes.
    [Show full text]
  • SUSE Linux Enterprise Server 15 SP2 Autoyast Guide Autoyast Guide SUSE Linux Enterprise Server 15 SP2
    SUSE Linux Enterprise Server 15 SP2 AutoYaST Guide AutoYaST Guide SUSE Linux Enterprise Server 15 SP2 AutoYaST is a system for unattended mass deployment of SUSE Linux Enterprise Server systems. AutoYaST installations are performed using an AutoYaST control le (also called a “prole”) with your customized installation and conguration data. Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see https://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents 1 Introduction to AutoYaST 1 1.1 Motivation 1 1.2 Overview and Concept 1 I UNDERSTANDING AND CREATING THE AUTOYAST CONTROL FILE 4 2 The AutoYaST Control
    [Show full text]
  • The Linux Storage Stack Diagram
    The Linux Storage Stack Diagram version 3.17, 2014-10-17 outlines the Linux storage stack as of Kernel version 3.17 ISCSI USB mmap Fibre Channel Fibre over Ethernet Fibre Channel Fibre Virtual Host Virtual FireWire (anonymous pages) Applications (Processes) LIO malloc vfs_writev, vfs_readv, ... ... stat(2) read(2) open(2) write(2) chmod(2) VFS tcm_fc sbp_target tcm_usb_gadget tcm_vhost tcm_qla2xxx iscsi_target_mod block based FS Network FS pseudo FS special Page ext2 ext3 ext4 proc purpose FS target_core_mod direct I/O NFS coda sysfs Cache (O_DIRECT) xfs btrfs tmpfs ifs smbfs ... pipefs futexfs ramfs target_core_file iso9660 gfs ocfs ... devtmpfs ... ceph usbfs target_core_iblock target_core_pscsi network optional stackable struct bio - sector on disk BIOs (Block I/O) BIOs (Block I/O) - sector cnt devices on top of “normal” - bio_vec cnt block devices drbd LVM - bio_vec index - bio_vec list device mapper mdraid dm-crypt dm-mirror ... dm-cache dm-thin bcache BIOs BIOs Block Layer BIOs I/O Scheduler blkmq maps bios to requests multi queue hooked in device drivers noop Software (they hook in like stacked ... Queues cfq devices do) deadline Hardware Hardware Dispatch ... Dispatch Queue Queues Request Request BIO based Drivers based Drivers based Drivers request-based device mapper targets /dev/nullb* /dev/vd* /dev/rssd* dm-multipath SCSI Mid Layer /dev/rbd* null_blk SCSI upper level drivers virtio_blk mtip32xx /dev/sda /dev/sdb ... sysfs (transport attributes) /dev/nvme#n# /dev/skd* rbd Transport Classes nvme skd scsi_transport_fc network
    [Show full text]
  • Effective Cache Apportioning for Performance Isolation Under
    Effective Cache Apportioning for Performance Isolation Under Compiler Guidance Bodhisatwa Chatterjee Sharjeel Khan Georgia Institute of Technology Georgia Institute of Technology Atlanta, USA Atlanta, USA [email protected] [email protected] Santosh Pande Georgia Institute of Technology Atlanta, USA [email protected] Abstract cache partitioning to divide the LLC among the co-executing With a growing number of cores per socket in modern data- applications in the system. Ideally, a cache partitioning centers where multi-tenancy of a diverse set of applications scheme obtains overall gains in system performance by pro- must be efficiently supported, effective sharing of the last viding a dedicated region of cache memory to high-priority level cache is a very important problem. This is challenging cache-intensive applications and ensures security against because modern workloads exhibit dynamic phase behaviour cache-sharing attacks by the notion of isolated execution in - their cache requirements & sensitivity vary across different an otherwise shared LLC. Apart from achieving superior execution points. To tackle this problem, we propose Com- application performance and improving system throughput CAS, a compiler guided cache apportioning system that pro- [7, 20, 31], cache partitioning can also serve a variety of pur- vides smart cache allocation to co-executing applications in a poses - improving system power and energy consumption system. The front-end of Com-CAS is primarily a compiler- [6, 23], ensuring fairness in resource allocation [26, 36] and framework equipped with learning mechanisms to predict even enabling worst case execution-time analysis of real-time cache requirements, while the backend consists of allocation systems [18].
    [Show full text]