DOCSLIB.ORG

Linux Fast-STREAMS Installation and Reference Manual Version 0.9.2 Edition 4 Updated 2008-10-31 Package Streams-0.9.2.4

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Linux Fast-STREAMS Installation and Reference Manual Version 0.9.2 Edition 4 Updated 2008-10-31 Package Streams-0.9.2.4 Linux Fast-STREAMS Installation and Reference Manual Version 0.9.2 Edition 4 Updated 2008-10-31 Package streams-0.9.2.4 Brian Bidulock <[email protected]> for The OpenSS7 Project <http://www.openss7.org/> Copyright c 2001-2008 OpenSS7 Corporation <http://www.openss7.com/> Copyright c 1997-2000 Brian F. G. Bidulock <[email protected]> All Rights Reserved. Published by OpenSS7 Corporation 1469 Jefferys Crescent Edmonton, Alberta T6L 6T1 Canada This is texinfo edition 4 of the Linux Fast-STREAMS manual, and is consistent with streams 0.9.2. This manual was developed under the OpenSS7 Project and was funded in part by OpenSS7 Corporation. Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the con- ditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another lan- guage, under the same conditions as for modified versions. i Short Contents Preface ::::::::::::::::::::::::::::::::::::::::::::::::: 1 Quick Start Guide :::::::::::::::::::::::::::::::::::::::: 9 1 Introduction :::::::::::::::::::::::::::::::::::::::: 15 2 Objective ::::::::::::::::::::::::::::::::::::::::::: 17 3 Reference ::::::::::::::::::::::::::::::::::::::::::: 21 4 Development :::::::::::::::::::::::::::::::::::::::: 37 5 Porting :::::::::::::::::::::::::::::::::::::::::::: 53 6 Conformance :::::::::::::::::::::::::::::::::::::::: 57 7 Releases :::::::::::::::::::::::::::::::::::::::::::: 61 8 Installation ::::::::::::::::::::::::::::::::::::::::: 85 9 Troubleshooting :::::::::::::::::::::::::::::::::::: 133 Licenses ::::::::::::::::::::::::::::::::::::::::::::::: 143 Indices :::::::::::::::::::::::::::::::::::::::::::::::: 177 iii Table of Contents Preface :::::::::::::::::::::::::::::::::::::::::::::: 1 Notice :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 Abstract :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 Objective :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 Intent :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 Audience::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 Revisions:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 2 Version Control :::::::::::::::::::::::::::::::::::::::::::::::::: 2 ISO 9000 Compliance :::::::::::::::::::::::::::::::::::::::::::: 4 Disclaimer :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 4 U.S. Government Restricted Rights ::::::::::::::::::::::::::::::: 5 Acknowledgements :::::::::::::::::::::::::::::::::::::::::::::::::: 5 Sponsors ::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 5 Contributors ::::::::::::::::::::::::::::::::::::::::::::::::::::: 6 Authors ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 6 Maintainer :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 6 Web Resources :::::::::::::::::::::::::::::::::::::::::::::::::::::: 6 Quick Start Guide :::::::::::::::::::::::::::::::::: 9 Linux Fast-STREAMS :::::::::::::::::::::::::::::::::::::::::::::: 9 Release :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 9 Prerequisites :::::::::::::::::::::::::::::::::::::::::::::::::::: 10 Installation ::::::::::::::::::::::::::::::::::::::::::::::::::::: 10 Brief Installation Instructions ::::::::::::::::::::::::::::::::::: 11 Detailed Installation Instructions :::::::::::::::::::::::::::::::: 12 1 Introduction ::::::::::::::::::::::::::::::::::: 15 1.1 Overview ::::::::::::::::::::::::::::::::::::::::::::::::::::: 15 1.2 Organization of this Manual::::::::::::::::::::::::::::::::::: 15 1.3 Conventions and Definitions ::::::::::::::::::::::::::::::::::: 15 2 Objective::::::::::::::::::::::::::::::::::::::: 17 2.1 Background ::::::::::::::::::::::::::::::::::::::::::::::::::: 17 2.2 What is STREAMS? :::::::::::::::::::::::::::::::::::::::::: 17 2.3 Why STREAMS? ::::::::::::::::::::::::::::::::::::::::::::: 18 2.4 Why STREAMS for Linux? ::::::::::::::::::::::::::::::::::: 18 2.5 History of STREAMS for Linux ::::::::::::::::::::::::::::::: 19 2.6 Why Fast? :::::::::::::::::::::::::::::::::::::::::::::::::::: 19 iv Linux Fast-STREAMS 3 Reference :::::::::::::::::::::::::::::::::::::: 21 3.1 Files :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 21 3.2 Drivers ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 23 3.3 Modules :::::::::::::::::::::::::::::::::::::::::::::::::::::: 26 3.4 Libraries :::::::::::::::::::::::::::::::::::::::::::::::::::::: 28 3.4.1 libstreams Library Routines :::::::::::::::::::::::::::::: 28 3.4.2 libLiS Library Routines :::::::::::::::::::::::::::::::::: 29 3.4.3 libpLiS Library Routines ::::::::::::::::::::::::::::::::: 30 3.4.4 Using the Library :::::::::::::::::::::::::::::::::::::::: 30 3.5 Utilities ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 31 3.5.1 Init Scripts::::::::::::::::::::::::::::::::::::::::::::::: 31 3.5.2 User Utilities::::::::::::::::::::::::::::::::::::::::::::: 31 3.5.3 Administrative Utilities :::::::::::::::::::::::::::::::::: 32 3.5.4 Performance Test Programs :::::::::::::::::::::::::::::: 34 3.5.5 Conformance Test Programs:::::::::::::::::::::::::::::: 35 4 Development ::::::::::::::::::::::::::::::::::: 37 4.1 Header Files :::::::::::::::::::::::::::::::::::::::::::::::::: 37 4.1.1 User Space Programs::::::::::::::::::::::::::::::::::::: 39 4.1.2 Kernel Space Drivers and Modules:::::::::::::::::::::::: 39 4.2 Libraries :::::::::::::::::::::::::::::::::::::::::::::::::::::: 39 4.3 Kernel Modules ::::::::::::::::::::::::::::::::::::::::::::::: 40 4.4 Manual Pages ::::::::::::::::::::::::::::::::::::::::::::::::: 40 5 Porting ::::::::::::::::::::::::::::::::::::::::: 53 5.1 Porting from LiS :::::::::::::::::::::::::::::::::::::::::::::: 54 5.2 Porting from SVR 4.2 MP::::::::::::::::::::::::::::::::::::: 55 5.3 Porting from Solaris::::::::::::::::::::::::::::::::::::::::::: 55 5.4 Porting from UnixWare ::::::::::::::::::::::::::::::::::::::: 55 5.5 Porting from Mentat :::::::::::::::::::::::::::::::::::::::::: 55 6 Conformance::::::::::::::::::::::::::::::::::: 57 6.1 Standards Compliance :::::::::::::::::::::::::::::::::::::::: 57 6.1.1 User Interface Compliance:::::::::::::::::::::::::::::::: 57 6.1.2 Service Interface Compliance ::::::::::::::::::::::::::::: 57 6.1.3 Kernel Interface Compliance:::::::::::::::::::::::::::::: 57 6.2 STREAMS Compatibility ::::::::::::::::::::::::::::::::::::: 58 v 7 Releases :::::::::::::::::::::::::::::::::::::::: 61 7.1 Prerequisites :::::::::::::::::::::::::::::::::::::::::::::::::: 61 7.2 Compatibility ::::::::::::::::::::::::::::::::::::::::::::::::: 61 7.2.1 GNU/Linux Distributions :::::::::::::::::::::::::::::::: 61 7.2.2 Kernel ::::::::::::::::::::::::::::::::::::::::::::::::::: 63 7.2.3 Architectures::::::::::::::::::::::::::::::::::::::::::::: 64 7.2.4 Linux STREAMS :::::::::::::::::::::::::::::::::::::::: 64 7.3 Release Notes ::::::::::::::::::::::::::::::::::::::::::::::::: 64 Major changes for release streams-0.9.2.4 :::::::::::::::::::::::: 64 Major changes for release streams-0.9.2.3 :::::::::::::::::::::::: 66 Major changes for release streams-0.9.2.2 :::::::::::::::::::::::: 67 Major changes for release streams-0.9.2.1 :::::::::::::::::::::::: 67 Major changes for release streams-0.7a.6.rc3 ::::::::::::::::::::: 68 Major changes for release streams-0.7a.6.rc2 ::::::::::::::::::::: 69 Major changes for release streams-0.7a.6rc1 :::::::::::::::::::::: 69 Major changes for release streams-0.7a.5 ::::::::::::::::::::::::: 69 Major changes for release streams-0.7a.4 ::::::::::::::::::::::::: 70 Major changes for release streams-0.7a.3 ::::::::::::::::::::::::: 70 Major changes for release streams-0.7a-3::::::::::::::::::::::::: 70 Major changes for release streams-0.7a-2::::::::::::::::::::::::: 70 Initial release streams-0.7a-1 :::::::::::::::::::::::::::::::::::: 70 7.4 Maturity :::::::::::::::::::::::::::::::::::::::::::::::::::::: 71 7.4.1 Pre-Alpha Releases::::::::::::::::::::::::::::::::::::::: 71 7.4.2 Alpha Releases ::::::::::::::::::::::::::::::::::::::::::: 71 7.4.3 Beta Releases :::::::::::::::::::::::::::::::::::::::::::: 72 7.4.4 Gamma Releases ::::::::::::::::::::::::::::::::::::::::: 72 7.4.5 Production Releases :::::::::::::::::::::::::::::::::::::: 72 7.4.6 Unstable Releases :::::::::::::::::::::::::::::::::::::::: 72 7.5 Bugs:::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 72 7.5.1 Defect Notices ::::::::::::::::::::::::::::::::::::::::::: 73 7.5.2 Known Defects ::::::::::::::::::::::::::::::::::::::::::: 73 7.5.3 Defect History ::::::::::::::::::::::::::::::::::::::::::: 73 7.6 Schedule :::::::::::::::::::::::::::::::::::::::::::::::::::::: 78 7.7 History ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 83 8 Installation::::::::::::::::::::::::::::::::::::: 85 8.1 Repositories::::::::::::::::::::::::::::::::::::::::::::::::::: 85 8.1.1 Repositories for YUM :::::::::::::::::::::::::::::::::::: 85 8.1.2 Repositories for APT::::::::::::::::::::::::::::::::::::: 86 8.2 Downloading :::::::::::::::::::::::::::::::::::::::::::::::::: 87 8.2.1 Downloading with YUM:::::::::::::::::::::::::::::::::: 87 8.2.2 Downloading with APT :::::::::::::::::::::::::::::::::: 89 8.2.3 Downloading the Binary RPM:::::::::::::::::::::::::::: 89 8.2.4 Downloading the Debian DEB ::::::::::::::::::::::::::::
Load more

Recommended publications
  • Timesys Linux Install HOWTO
    TimeSys Linux Install HOWTO Trevor Harmon <[email protected]> 2005−04−05 Revision History Revision 1.0 2005−04−05 Revised by: TH first official release This document is a quick−start guide for installing TimeSys Linux on a typical desktop workstation. TimeSys Linux Install HOWTO Table of Contents 1. Introduction.....................................................................................................................................................1 1.1. Background.......................................................................................................................................1 1.2. Copyright and License......................................................................................................................1 1.3. Disclaimer.........................................................................................................................................2 1.4. Feedback...........................................................................................................................................2 2. Requirements...................................................................................................................................................3 3. Install the packages.........................................................................................................................................4 4. Prepare the source directories.......................................................................................................................5 5. Configure
    [Show full text]
  • SYSTEM V RELEASE 4 Migration Guide
    - ATlaT UN/~ SYSTEM V RELEASE 4 Migration Guide UNIX Software Operation Copyright 1990,1989,1988,1987,1986,1985,1984,1983 AT&T All Rights Reserved Printed In USA Published by Prentice-Hall, Inc. A Division of Simon & Schuster Englewood Cliffs, New Jersey 07632 No part of this publication may be reproduced or transmitted in any form or by any means-graphic, electronic, electrical, mechanical, or chemical, including photocopying, recording in any medium, tap­ ing, by any computer or information storage and retrieval systems, etc., without prior permissions in writing from AT&T. IMPORTANT NOTE TO USERS While every effort has been made to ensure the accuracy of all information in this document, AT&T assumes no liability to any party for any loss or damage caused by errors or omissions or by state­ ments of any kind in this document, its updates, supplements, or special editions, whether such er­ rors are omissions or statements resulting from negligence, accident, or any other cause. AT&T furth­ er assumes no liability arising out of the application or use of any product or system described herein; nor any liability for incidental or consequential damages arising from the use of this docu­ ment. AT&T disclaims all warranties regarding the information contained herein, whether expressed, implied or statutory, including implied warranties of merchantability or fitness for a particular purpose. AT&T makes no representation that the interconnection of products in the manner described herein will not infringe on existing or future patent rights, nor do the descriptions contained herein imply the granting or license to make, use or sell equipment constructed in accordance with this description.
    [Show full text]
  • The Linux Device File-System
    The Linux Device File-System Richard Gooch EMC Corporation [email protected] Abstract 1 Introduction All Unix systems provide access to hardware via de- vice drivers. These drivers need to provide entry points for user-space applications and system tools to access the hardware. Following the \everything is a file” philosophy of Unix, these entry points are ex- posed in the file name-space, and are called \device The Device File-System (devfs) provides a power- special files” or \device nodes". ful new device management mechanism for Linux. Unlike other existing and proposed device manage- This paper discusses how these device nodes are cre- ment schemes, it is powerful, flexible, scalable and ated and managed in conventional Unix systems and efficient. the limitations this scheme imposes. An alternative mechanism is then presented. It is an alternative to conventional disc-based char- acter and block special devices. Kernel device drivers can register devices by name rather than de- vice numbers, and these device entries will appear in the file-system automatically. 1.1 Device numbers Devfs provides an immediate benefit to system ad- ministrators, as it implements a device naming scheme which is more convenient for large systems Conventional Unix systems have the concept of a (providing a topology-based name-space) and small \device number". Each instance of a driver and systems (via a device-class based name-space) alike. hardware component is assigned a unique device number. Within the kernel, this device number is Device driver authors can benefit from devfs by used to refer to the hardware and driver instance.
    [Show full text]
  • Fast Linux I/O in the Unix Tradition
    — preprint only: final version will appear in OSR, July 2008 — PipesFS: Fast Linux I/O in the Unix Tradition Willem de Bruijn Herbert Bos Vrije Universiteit Amsterdam Vrije Universiteit Amsterdam and NICTA [email protected] [email protected] ABSTRACT ory wall” [26]). To improve throughput, it is now essential This paper presents PipesFS, an I/O architecture for Linux to avoid all unnecessary memory operations. Inefficient I/O 2.6 that increases I/O throughput and adds support for het- primitives exacerbate the effects of the memory wall by in- erogeneous parallel processors by (1) collapsing many I/O curring unnecessary copying and context switching, and as interfaces onto one: the Unix pipeline, (2) increasing pipe a result of these cache misses. efficiency and (3) exploiting pipeline modularity to spread computation across all available processors. Contribution. We revisit the Unix pipeline as a generic model for streaming I/O, but modify it to reduce overhead, PipesFS extends the pipeline model to kernel I/O and com- extend it to integrate kernel processing and complement it municates with applications through a Linux virtual filesys- with support for anycore execution. We link kernel and tem (VFS), where directory nodes represent operations and userspace processing through a virtual filesystem, PipesFS, pipe nodes export live kernel data. Users can thus interact that presents kernel operations as directories and live data as with kernel I/O through existing calls like mkdir, tools like pipes. This solution avoids new interfaces and so unlocks all grep, most languages and even shell scripts.
    [Show full text]
  • Implantación De Linux Sobre Microcontroladores
    Embedded Linux system development Embedded Linux system development DSI Embedded Linux Free Electrons Developers © Copyright 2004-2018, Free Electrons. Creative Commons BY-SA 3.0 license. Latest update: March 14, 2018. Document updates and sources: http://free-electrons.com/doc/training/embedded-linux Corrections, suggestions, contributions and translations are welcome! DSI - FCEIA http://dsi.fceia.unr.edu.ar 1/263 Derechos de copia © Copyright 2018, Luciano Diamand Licencia: Creative Commons Attribution - Share Alike 3.0 http://creativecommons.org/licenses/by-sa/3.0/legalcode Ud es libre de: I copiar, distribuir, mostrar y realizar el trabajo I hacer trabajos derivados I hacer uso comercial del trabajo Bajo las siguientes condiciones: I Atribuci´on. Debes darle el cr´editoal autor original. I Compartir por igual. Si altera, transforma o construye sobre este trabajo, usted puede distribuir el trabajo resultante solamente bajo una licencia id´enticaa ´esta. I Para cualquier reutilizaci´ono distribuci´on,debe dejar claro a otros los t´erminos de la licencia de este trabajo. I Se puede renunciar a cualquiera de estas condiciones si usted consigue el permiso del titular de los derechos de autor. El uso justo y otros derechos no se ven afectados por lo anterior. DSI - FCEIA http://dsi.fceia.unr.edu.ar 2/263 Hiperv´ınculosen el documento Hay muchos hiperv´ınculosen el documento I Hiperv´ıncluosregulares: http://kernel.org/ I Enlaces a la documentaci´ondel Kernel: Documentation/kmemcheck.txt I Enlaces a los archivos fuente y directorios del kernel: drivers/input include/linux/fb.h I Enlaces a declaraciones, definiciones e instancias de los simbolos del kernel (funciones, tipos, datos, estructuras): platform_get_irq() GFP_KERNEL struct file_operations DSI - FCEIA http://dsi.fceia.unr.edu.ar 3/263 Introducci´ona Linux Embebido Introducci´ona DSI Linux Embebido Embedded Linux Developers Free Electrons © Copyright 2004-2018, Free Electrons.
    [Show full text]
  • Introduction to the Linux for HPC
    Introduction to the Linux for HPC Basic Linux for Beginner HPC Users Purpose of This Lecture • Fundamentals of using Linux and Linux-like systems on HPC systems • History of Linux • Shell and basic commands • File, data and process management and utilities History of Linux Linux in the Real World 95% Top500 are Linux-like Operating System # of Systems Percentage Linux 456 91.20% Unix 22 4.40% Windows 6 1.20% BSD Based 1 0.20% Mixed 15 3.00% Unix A Little History • Q: How old is Unix (5, 10, 20 years, or greater)? A: > 40 Years • Unix dates back to 1969 with a group at Bell Laboratories • The original Unix operating system was written in assembler • First 1972 Unix installations had 3 users and a 500KB disk DEC PDP-11, 1972 Linux Bringing Unix to the Desktop • Unix was very expensive • MINIX, tried but was not a full port • An open source solution was needed! 1990’s Movers and Shakers Richard Stallman, father of the GNU Project Linus Torvalds What is Linux? • Linux is a clone of the Unix operating system written from scratch by Linus Torvalds with assistance from developers around the globe (technically speaking, Linux is not Unix) • Torvalds uploaded the first version - 0.01 in September 1991 • Only about 2% of the current Linux kernel is written by Torvalds himself but he remains the ultimate authority on what new code is incorporated into the Linux kernel. • Developed under the GNU General Public License , the source code for Linux is freely available • A large number of Linux-based distributions exist (for free or purchase) Why use LINUX? • Performance: as we’ve seen, supercomputers generally run Linux; rich-multi user environment • Functionality: a number of community driven scientific applications and libraries are developed under Linux (molecular dynamics, linear algebra, fast-fourier transforms, etc).
    [Show full text]
  • Linux 2.5 Kernel Developers Summit
    conference reports This issue’s reports are on the Linux 2.5 Linux 2.5 Kernel Developers Linux development, but I certainly Kernel Developers Summit Summit thought that, in all of this time, someone would have brought this group together OUR THANKS TO THE SUMMARIZER: SAN JOSE, CALIFORNIA before. Rik Farrow, with thanks to La Monte MARCH 30-31, 2001 Yarroll and Chris Mason for sharing their Summarized by Rik Farrow Another difference appeared when the notes. first session started on Friday morning. The purpose of this workshop was to The conference room was set up with cir- provide a forum for discussion of cular tables, each with power strips for changes to be made in the 2.5 release of For additional information on the Linux laptops, and only a few attendees were Linux (a trademark of Linus Torvalds). I not using a laptop. USENIX had pro- 2.5 Kernel Developers Summit, see the assume that many people reading this vided Aeronet wireless setup via the following sites: will be familiar with Linux, and I will hotel’s T1 link, and people were busy <http://lwn.net/2001/features/KernelSummit/> attempt to explain things that might be typing and compiling. Chris Mason of unfamiliar to others. That said, the odd- <http://cgi.zdnet.com/slink?91362:12284618> OSDN noticed that Dave Miller had numbered releases, like 2.3 and now 2.5, <http://www.osdn.com/conferences/kernel/> written a utility to modulate the speed of are development releases where the the CPU fans based upon the tempera- intent is to try out new features or make ture reading from his motherboard.
    [Show full text]
  • UNIX History Page 1 Tuesday, December 10, 2002 7:02 PM
    UNIX History Page 1 Tuesday, December 10, 2002 7:02 PM CHAPTER 1 UNIX Evolution and Standardization This chapter introduces UNIX from a historical perspective, showing how the various UNIX versions have evolved over the years since the very first implementation in 1969 to the present day. The chapter also traces the history of the different attempts at standardization that have produced widely adopted standards such as POSIX and the Single UNIX Specification. The material presented here is not intended to document all of the UNIX variants, but rather describes the early UNIX implementations along with those companies and bodies that have had a major impact on the direction and evolution of UNIX. A Brief Walk through Time There are numerous events in the computer industry that have occurred since UNIX started life as a small project in Bell Labs in 1969. UNIX history has been largely influenced by Bell Labs’ Research Editions of UNIX, AT&T’s System V UNIX, Berkeley’s Software Distribution (BSD), and Sun Microsystems’ SunOS and Solaris operating systems. The following list shows the major events that have happened throughout the history of UNIX. Later sections describe some of these events in more detail. 1 UNIX History Page 2 Tuesday, December 10, 2002 7:02 PM 2 UNIX Filesystems—Evolution, Design, and Implementation 1969. Development on UNIX starts in AT&T’s Bell Labs. 1971. 1st Edition UNIX is released. 1973. 4th Edition UNIX is released. This is the first version of UNIX that had the kernel written in C. 1974. Ken Thompson and Dennis Ritchie publish their classic paper, “The UNIX Timesharing System” [RITC74].
    [Show full text]
  • Fstream: Managing Flash Streams in the File System
    FStream: Managing Flash Streams in the File System Eunhee Rho, Kanchan Joshi, Seung-Uk Shin, Nitesh Jagadeesh Shetty, Joo-Young Hwang, Sangyeun Cho, Daniel DG Lee, and Jaeheon Jeong, Samsung Electronics. Co., Ltd. https://www.usenix.org/conference/fast18/presentation/rho This paper is included in the Proceedings of the 16th USENIX Conference on File and Storage Technologies. February 12–15, 2018 • Oakland, CA, USA ISBN 978-1-931971-42-3 Open access to the Proceedings of the 16th USENIX Conference on File and Storage Technologies is sponsored by USENIX. FStream: Managing Flash Streams in the File System Eunhee Rho, Kanchan Joshi, Seung-Uk Shin, Nitesh Jagadeesh Shetty Joo-Young Hwang, Sangyeun Cho, Daniel DG Lee, Jaeheon Jeong Samsung Electronics Co., Ltd. Abstract out issue [3,7]. To the same end, we focus on how to take The performance and lifespan of a solid-state drive advantage of the multi-streamed SSD mechanism [8]. (SSD) depend not only on the current input workload This mechanism opens up a way to dictate data place- but also on its internal media fragmentation formed over ment on an SSD’s underlying physical media, abstracted time, as stale data are spread over a wide range of phys- by streams. In principle, if the host system perfectly ical space in an SSD. The recently proposed streams maps data having the same lifetime to the same streams, gives a means for the host system to control how data are an SSD’s write amplification becomes one, completely placed on the physical media (abstracted by a stream) eliminating the media fragmentation problem.
    [Show full text]
  • Veritas Backup Exec from Arcserve Netware.Pdf
    for NetWare Using v8.5 of VERITAS Backup Exec™ for NetWare’s Enhanced ARCserveIT Tape Read Feature With this release, Backup Exec for NetWare extends its ability to read ARCserveIT tapes, allowing you to more easily migrate from ARCserveIT to Backup Exec and to restore data from ARCserveIT tapes. Backup Exec will read: • ARCserveIT for NetWare versions 4.x, 5.x, and 6.x • ARCserveIT for Windows NT version 6.x • ARCserveIT’s native tape format • ARCserveIT’s embedded SMS tape format How the Enhanced ARCserveIT Tape Read Works When backing up a NetWare server, ARCserveIT 6.x by default includes Novell’s SMS data streams within the ARCserveIT format, allowing ARCserveIT to get its data stream from a Novell TSA. ARCserveIT then packages this data stream within the ARCserveIT format and places this data on tape. To read the data, Backup Exec unpackages the original TSA data and sends it back to the Novell TSA for interpretation. The NetWare server files and directories backed up by ARCserveIT can thus be fully restored by Backup Exec. Special Limitations If the default for ARCserveIT is changed so that ARCserveIT does not use SMS for backing up NetWare servers, the backup sets on the tape will be in ARCserveIT’s native format. Backup Exec will restore file and directory data, but will not always restore the long name for files. Other limitations are that Backup Exec cannot read the following: • ARCserveIT backup sets that are software compressed, software encrypted, or interleaved • ARCserveIT backups of NDS data sets • ARCserveIT backups of the NT registry • ARCserveIT backups of Microsoft Exchange or Microsoft SQL data Note NDS backups rapidly become out of date; therefore, you probably would not be restoring ARCserveIT backups of NDS data using Backup Exec.
    [Show full text]
  • COS 318: Operating Systems I/O Device Interactions and Drivers
    Topics COS 318: Operating Systems u So far: l Management of CPU and concurrency l Management of main memory and virtual memory I/O Device Interactions and u Next: Management of the I/O system Drivers l Interacting with I/O devices l Device drivers Jaswinder Pal Singh l Storage Devices Computer Science Department Princeton University u Then, File Systems l File System Structure (http://www.cs.princeton.edu/courses/cos318/) l Naming and Directories l Efficiency/Performance l Reliability and Protection 2 Input and Output Revisit Hardware u A computer u Compute hardware CPU l CPU cores and caches CPU l Computation (CPU, memory hierarchy) CPUCPU CPU l Memory $ l Move data into and out of a system (locketween I/O devices Chip l I/O and memory hierarchy) l Controllers and logic Memory I/O bridge u Challenges with I/O devices I/O bus l Different categories with different characteristics: storage, u I/O Hardware networking, displays, keyboard, mouse ... l I/O bus or interconnect l Large number of device drivers to support l I/O device l I/O controller or adapter l Device drivers run in kernel mode and can crash systems • Often on parent board Network u Goals of the OS • Cable connects it to device • Often using standard interfaces: IDE, l Provide a generic, consistent, convenient and reliable way to SATA, SCSI, USB, FireWire… access I/O devices • Has registers for control, data signals • Processor gives commands and/or l Achieve potential I/O performance in a system data to controller to do I/O • Special I/O instructions (w.
    [Show full text]
  • CRUX Handbook RELEASE 2.0 CRUX Handbook: RELEASE 2.0
    CRUX Handbook RELEASE 2.0 CRUX Handbook: RELEASE 2.0 Published 2004-06-01 Copyright © 2001, 2002, 2003, 2004 Per Lidén [mailto:[email protected]] This handbook covers the installation, configuration and administration of CRUX. Please note that this hand- book only covers topics that are specific to CRUX [http://crux.nu/]. For further information about Linux see the Linux Documentation Project [http://www.tldp.org/]. Table of Contents Preface...................................................................................................................................5 1.Introduction .........................................................................................................................1 1.1.WhatisCRUX? ......................................................................................................... 1 1.2. Why use CRUX? ........................................................................................................ 1 1.3.License ....................................................................................................................1 1.3.1.Packages ........................................................................................................ 1 1.3.2. Build Scripts ................................................................................................... 1 1.3.3. NO WARANTY .............................................................................................. 1 2. Installing CRUX ..................................................................................................................
    [Show full text]