DOCSLIB.ORG

IBM Spectrum Scale Frequently Asked Questions and Answers

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IBM Spectrum Scale Frequently Asked Questions and Answers IBM Spectrum Scale Frequently Asked Questions and Answers IBM Spectrum Scale Overview IBM Spectrum® Scale, based on technology from IBM® General Parallel File System (hereinafter referred to as IBM Spectrum Scale or GPFS), is a high performance shared-disk file management solution that provides fast, reliable access to data from multiple servers. Applications can readily access files using standard file system interfaces, and the same file can be accessed concurrently from multiple servers and protocols. IBM Spectrum Scale is designed to provide high availability through advanced clustering technologies, dynamic file system management, and data replication. IBM Spectrum Scale can continue to provide data access even when the cluster experiences storage or server malfunctions. IBM Spectrum Scale scalability and performance are designed for data intensive applications such as cloud storage engineering design, digital media, data mining, relational databases, financial analytics, seismic data processing, scientific research and scalable file serving. IBM Spectrum Scale is supported on AIX®, Linux®, and Windows Server operating systems. It is supported on IBM POWER®, Intel or AMD Opteron based servers, and IBM Z®. For more information on the capabilities of IBM Spectrum Scale and its applicability to your environment, see the IBM Spectrum Scale: Concepts, Planning, and Installation Guide. Important References • List of Q&As • IBM Spectrum Scale functional support information • Supported Upgrade Paths on page 10 • Software Version Recommendation Preventive Service Planning IBM Spectrum Scale FAQ These IBM Spectrum Scale Frequently Asked Questions and Answers provides you the most up-to-date information on topics including ordering IBM Spectrum Scale, supported platforms, and supported configuration sizes and capacities. This FAQ is maintained on a regular basis and must be referenced before any system upgrades or major configuration changes to your IBM Spectrum Scale cluster. We welcome your feedback, if you have any comments, suggestions or questions regarding the information provided here send email to [email protected]. Updates to this FAQ include: Table 1: May 2021 FAQ updates May 2021 2.35 Has file immutability been assessed for compliance? Table 2: April 2021 FAQ updates April 2021 2.1 What is supported on IBM Spectrum Scale for AIX, Linux, Power®, and Windows? 2.15 What are the current limitations and advisories for using Scale Out Backup and Restore (SOBAR)? 4.12 What are the considerations for using block storage systems that support thinly provisioned volumes (thin provisioning)? 9.2 What versions of Hadoop are supported by IBM Spectrum scale version? 9.3 What Hadoop distributions are supported by IBM Spectrum Scale? 9.5 Can Hadoop connector be used for IBM Spectrum Scale that has shared storage (including the Elastic Storage Server)? 9.6 Can Hadoop connector be used for IBM Spectrum Scale that has shared storage (including ESS) and internal storage (FPO pool) in the same file system? 9.9 What are the differences between the Hadoop connector and the HDFS Transparency connector ? 16.2 Is the message queue still supported in IBM Spectrum Scale 5.1.1? 17.5 How can one identify which filesets in IBM Spectrum Scale are created by the IBM Spectrum Scale CSI driver? 17.8 Where can I get more information about the subjects discussed in this section? 18.14 Are there any extra requirements for using or configuring NVMe drives for use with IBM Spectrum Scale Erasure Code Edition? 1 Table 3: March 2021 FAQ updates March 2021 1.7 Does IBM Spectrum Scale have a trial program? 2.1 What is supported on IBM Spectrum Scale for AIX, Linux, Power, and Windows? 2.8 Can different IBM Spectrum Scale maintenance levels coexist? 3.1 What are the minimum hardware requirements for an IBM Spectrum Scale cluster? 6.3 Are there any considerations when utilizing the Remote Direct Memory Access (RDMA)? 7.3 Is IBM Spectrum Scale on Linux (x86 and Power) supported in a virtualization environment? 20.4 What is the impact on IBM Spectrum Scale Protocol when you are using AD with RFC2307 or migrating to Windows 2016 AD server or later? Table 4: February 2021 FAQ updates February 2021 1.5 Does IBM Spectrum Scale participate in the IBM Academic Initiative Program? 2.1 What is supported on IBM Spectrum Scale for AIX, Linux, Power, and Windows? 2.3 What are the current restrictions on IBM Spectrum Scale Linux kernel support? 6.2 What configuration and performance tuning suggestions are there for GPFS when used primarily for Oracle databases? Table 5: January 2021 FAQ updates January 2021 2.1 What is supported on IBM Spectrum Scale for AIX, Linux, Power, and Windows? 3.1 What are the minimum hardware requirements for an IBM Spectrum Scale cluster? 6.7 Does IBM Spectrum Scale use OpenSSL for RPC secure communication? 6.8 What ciphers are supported for use by IBM Spectrum Scale? 7.7 Does IBM Spectrum Scale support exploitation of the Virtual I/O Server (VIOS) features of POWER processors? 10.16 Are OpenStack package repositories required to install the Object protocol? 17.1 Can IBM Spectrum Scale storage be utilized inside of containerized environments? 17.4 Can Kubernetes perform a health check on the underlying IBM Spectrum Scale cluster? 17.6 Can I use IBM ESS storage to provision volumes into my remote cluster and then act upon these volumes with IBM Spectrum Scale CSI? 17.7 Is it possible to contribute to the IBM Spectrum Scale CSI driver or operator projects? 17.8 Where can I get more information about the subjects discussed in this section? Table 6: December 2020 FAQ updates December 2020 2.1 What is supported on IBM Spectrum Scale for AIX, Linux, Power, and Windows? Table 7: November 2020 FAQ updates November 2020 1.7 Does IBM Spectrum Scale have a trial program? 2 Table 7: November 2020 FAQ updates (continued) November 2020 2.1 What is supported on IBM Spectrum Scale for AIX, Linux, Power, and Windows? 2.12 What are the requirements/limitations for using native encryption in IBM Spectrum Scale Advanced Edition or Data Management Edition? 2.16 What are the current limitations for using the File Placement Optimizer (FPO) function? 2.25 What are the current requirements/limitations for IBM Spectrum Scale for Linux on Z? 2.29 What are the requirements/limitations for using the compression function? 2.35 Has file immutability been assessed for compliance? 2.36 Is there any guidance for RHEL 8 installations on IBM Spectrum Scale? 2.39 Are IBM Spectrum Scale packages signed by IBM? 8.1 What are the requirements to use the protocol access methods integrated with IBM Spectrum Scale V4.1.1 and later? 9.2 What versions of Hadoop are supported by IBM Spectrum scale version? 9.3 What Hadoop distributions are supported by IBM Spectrum Scale? 9.5 Can Hadoop connector be used for IBM Spectrum Scale that has shared storage (including the Elastic Storage Server)? 9.7 What open-source Hadoop components are certified using IBM Spectrum Scale connector? 9.10 What are the requirements/limitations for using the IBM Spectrum Scale HDFS Transparency connector? 10.1 What considerations are there when using OpenStack Software with IBM Spectrum Scale? 10.2 What are the new features of IBM Spectrum Scale for Object Storage? 10.15 Does the Object protocol support immutable objects? 13.10 What are IBM Spectrum Scale OEMs, and how are their products licensed? 13.11 Can I get support for IBM Spectrum Scale from IBM if it is supplied as part of an OEM solution? 13.12 If I install IBM Spectrum Scale software and licenses from IBM on an OEM system from another vendor, is that software supported by IBM? 13.13 Can I mix products licensed from other vendors that embed IBM Spectrum Scale (OEMs) in the same cluster as IBM Spectrum Scale licenses from IBM? 18.2 What are the limitations of IBM Spectrum Scale Erasure Code Edition? 18.4.4 What operating systems are supported for IBM Spectrum Scale Erasure Code Edition storage servers? Table 8: October 2020 FAQ updates October 2020 5.17 What is the current maximum IBM Spectrum Scale file size limit? 7.3 Is IBM Spectrum Scale on Linux (x86 and Power) supported in a virtualization environment? Table 9: July 2020 FAQ updates July 2020 2.39 Are IBM Spectrum Scale packages signed by IBM? Table 10: June 2020 FAQ updates June 2020 2.12 What are the requirements/limitations for using native encryption in IBM Spectrum Scale Advanced Edition or Data Management Edition? 3 Table 10: June 2020 FAQ updates (continued) June 2020 6.12 How should IBM Spectrum Scale Advanced Edition or Data Management Edition be configured to only use FIPS 140-2- certified cryptographic engines? Table 11: May 2020 FAQ updates May 2020 2.7 What are the requirements for the use of OpenSSH on Windows nodes? 2.31 What considerations are there when running on SELinux? 2.36 Is there any guidance for RHEL 8 installations on IBM Spectrum Scale? 7.5 Is IBM Spectrum Scale on Windows supported in a virtualization environment? 7.11 Are there any limitations for using IBM Spectrum Scale in a virtualization environment? 8.1 What are the requirements to use the protocol access methods integrated with IBM Spectrum Scale V4.1.1 and later? 9.1 What platforms are supported for Hadoop on IBM Spectrum Scale? 9.2 What versions of Hadoop are supported by IBM Spectrum scale version? 9.3 What Hadoop distributions are supported by IBM Spectrum Scale? 9.4 What IBM Spectrum Scale licenses do I need to use the IBM Spectrum Scale Hadoop connector? 9.5 Can Hadoop connector be used for IBM Spectrum Scale that
Load more

Recommended publications
  • Elastic Storage for Linux on System Z IBM Research & Development Germany
    Peter Münch T/L Test and Development – Elastic Storage for Linux on System z IBM Research & Development Germany Elastic Storage for Linux on IBM System z © Copyright IBM Corporation 2014 9.0 Elastic Storage for Linux on System z Session objectives • This presentation introduces the Elastic Storage, based on General Parallel File System technology that will be available for Linux on IBM System z. Understand the concepts of Elastic Storage and which functions will be available for Linux on System z. Learn how you can integrate and benefit from the Elastic Storage in a Linux on System z environment. Finally, get your first impression in a live demo of Elastic Storage. 2 © Copyright IBM Corporation 2014 Elastic Storage for Linux on System z Trademarks The following are trademarks of the International Business Machines Corporation in the United States and/or other countries. AIX* FlashSystem Storwize* Tivoli* DB2* IBM* System p* WebSphere* DS8000* IBM (logo)* System x* XIV* ECKD MQSeries* System z* z/VM* * Registered trademarks of IBM Corporation The following are trademarks or registered trademarks of other companies. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
    [Show full text]
  • Beej's Guide to Unix IPC
    Beej's Guide to Unix IPC Brian “Beej Jorgensen” Hall [email protected] Version 1.1.3 December 1, 2015 Copyright © 2015 Brian “Beej Jorgensen” Hall This guide is written in XML using the vim editor on a Slackware Linux box loaded with GNU tools. The cover “art” and diagrams are produced with Inkscape. The XML is converted into HTML and XSL-FO by custom Python scripts. The XSL-FO output is then munged by Apache FOP to produce PDF documents, using Liberation fonts. The toolchain is composed of 100% Free and Open Source Software. Unless otherwise mutually agreed by the parties in writing, the author offers the work as-is and makes no representations or warranties of any kind concerning the work, express, implied, statutory or otherwise, including, without limitation, warranties of title, merchantibility, fitness for a particular purpose, noninfringement, or the absence of latent or other defects, accuracy, or the presence of absence of errors, whether or not discoverable. Except to the extent required by applicable law, in no event will the author be liable to you on any legal theory for any special, incidental, consequential, punitive or exemplary damages arising out of the use of the work, even if the author has been advised of the possibility of such damages. This document is freely distributable under the terms of the Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 License. See the Copyright and Distribution section for details. Copyright © 2015 Brian “Beej Jorgensen” Hall Contents 1. Intro................................................................................................................................................................1 1.1. Audience 1 1.2. Platform and Compiler 1 1.3.
    [Show full text]
  • Mmap and Dma
    CHAPTER THIRTEEN MMAP AND DMA This chapter delves into the area of Linux memory management, with an emphasis on techniques that are useful to the device driver writer. The material in this chap- ter is somewhat advanced, and not everybody will need a grasp of it. Nonetheless, many tasks can only be done through digging more deeply into the memory man- agement subsystem; it also provides an interesting look into how an important part of the kernel works. The material in this chapter is divided into three sections. The first covers the implementation of the mmap system call, which allows the mapping of device memory directly into a user process’s address space. We then cover the kernel kiobuf mechanism, which provides direct access to user memory from kernel space. The kiobuf system may be used to implement ‘‘raw I/O’’ for certain kinds of devices. The final section covers direct memory access (DMA) I/O operations, which essentially provide peripherals with direct access to system memory. Of course, all of these techniques requir e an understanding of how Linux memory management works, so we start with an overview of that subsystem. Memor y Management in Linux Rather than describing the theory of memory management in operating systems, this section tries to pinpoint the main features of the Linux implementation of the theory. Although you do not need to be a Linux virtual memory guru to imple- ment mmap, a basic overview of how things work is useful. What follows is a fairly lengthy description of the data structures used by the kernel to manage memory.
    [Show full text]
  • An Introduction to Linux IPC
    An introduction to Linux IPC Michael Kerrisk © 2013 linux.conf.au 2013 http://man7.org/ Canberra, Australia [email protected] 2013-01-30 http://lwn.net/ [email protected] man7 .org 1 Goal ● Limited time! ● Get a flavor of main IPC methods man7 .org 2 Me ● Programming on UNIX & Linux since 1987 ● Linux man-pages maintainer ● http://www.kernel.org/doc/man-pages/ ● Kernel + glibc API ● Author of: Further info: http://man7.org/tlpi/ man7 .org 3 You ● Can read a bit of C ● Have a passing familiarity with common syscalls ● fork(), open(), read(), write() man7 .org 4 There’s a lot of IPC ● Pipes ● Shared memory mappings ● FIFOs ● File vs Anonymous ● Cross-memory attach ● Pseudoterminals ● proc_vm_readv() / proc_vm_writev() ● Sockets ● Signals ● Stream vs Datagram (vs Seq. packet) ● Standard, Realtime ● UNIX vs Internet domain ● Eventfd ● POSIX message queues ● Futexes ● POSIX shared memory ● Record locks ● ● POSIX semaphores File locks ● ● Named, Unnamed Mutexes ● System V message queues ● Condition variables ● System V shared memory ● Barriers ● ● System V semaphores Read-write locks man7 .org 5 It helps to classify ● Pipes ● Shared memory mappings ● FIFOs ● File vs Anonymous ● Cross-memory attach ● Pseudoterminals ● proc_vm_readv() / proc_vm_writev() ● Sockets ● Signals ● Stream vs Datagram (vs Seq. packet) ● Standard, Realtime ● UNIX vs Internet domain ● Eventfd ● POSIX message queues ● Futexes ● POSIX shared memory ● Record locks ● ● POSIX semaphores File locks ● ● Named, Unnamed Mutexes ● System V message queues ● Condition variables ● System V shared memory ● Barriers ● ● System V semaphores Read-write locks man7 .org 6 It helps to classify ● Pipes ● Shared memory mappings ● FIFOs ● File vs Anonymous ● Cross-memoryn attach ● Pseudoterminals tio a ● proc_vm_readv() / proc_vm_writev() ● Sockets ic n ● Signals ● Stream vs Datagram (vs uSeq.
    [Show full text]
  • IBM Spectrum Scale CSI Driver for Container Persistent Storage
    Front cover IBM Spectrum Scale CSI Driver for Container Persistent Storage Abhishek Jain Andrew Beattie Daniel de Souza Casali Deepak Ghuge Harald Seipp Kedar Karmarkar Muthu Muthiah Pravin P. Kudav Sandeep R. Patil Smita Raut Yadavendra Yadav Redpaper IBM Redbooks IBM Spectrum Scale CSI Driver for Container Persistent Storage April 2020 REDP-5589-00 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. First Edition (April 2020) This edition applies to Version 5, Release 0, Modification 4 of IBM Spectrum Scale. © Copyright International Business Machines Corporation 2020. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. iii iv IBM Spectrum Scale CSI Driver for Container Persistent Storage Contents Notices . vii Trademarks . viii Preface . ix Authors. ix Now you can become a published author, too . xi Comments welcome. xii Stay connected to IBM Redbooks . xii Chapter 1. IBM Spectrum Scale and Containers Introduction . 1 1.1 Abstract . 2 1.2 Assumptions . 2 1.3 Key concepts and terminology . 3 1.3.1 IBM Spectrum Scale . 3 1.3.2 Container runtime . 3 1.3.3 Container Orchestration System. 4 1.4 Introduction to persistent storage for containers Flex volumes. 4 1.4.1 Static provisioning. 4 1.4.2 Dynamic provisioning . 4 1.4.3 Container Storage Interface (CSI). 5 1.4.4 Advantages of using IBM Spectrum Scale storage for containers . 5 Chapter 2. Architecture of IBM Spectrum Scale CSI Driver . 7 2.1 CSI Component Overview. 8 2.2 IBM Spectrum Scale CSI driver architecture.
    [Show full text]
  • 11.7 the Windows 2000 File System
    830 CASE STUDY 2: WINDOWS 2000 CHAP. 11 11.7 THE WINDOWS 2000 FILE SYSTEM Windows 2000 supports several file systems, the most important of which are FAT-16, FAT-32, and NTFS (NT File System). FAT-16 is the old MS-DOS file system. It uses 16-bit disk addresses, which limits it to disk partitions no larger than 2 GB. FAT-32 uses 32-bit disk addresses and supports disk partitions up to 2 TB. NTFS is a new file system developed specifically for Windows NT and car- ried over to Windows 2000. It uses 64-bit disk addresses and can (theoretically) support disk partitions up to 264 bytes, although other considerations limit it to smaller sizes. Windows 2000 also supports read-only file systems for CD-ROMs and DVDs. It is possible (even common) to have the same running system have access to multiple file system types available at the same time. In this chapter we will treat the NTFS file system because it is a modern file system unencumbered by the need to be fully compatible with the MS-DOS file system, which was based on the CP/M file system designed for 8-inch floppy disks more than 20 years ago. Times have changed and 8-inch floppy disks are not quite state of the art any more. Neither are their file systems. Also, NTFS differs both in user interface and implementation in a number of ways from the UNIX file system, which makes it a good second example to study. NTFS is a large and complex system and space limitations prevent us from covering all of its features, but the material presented below should give a reasonable impression of it.
    [Show full text]
  • “Application - File System” Divide with Promises
    Bridging the “Application - File System” divide with promises Raja Bala Computer Sciences Department University of Wisconsin, Madison, WI [email protected] Abstract that hook into the file system and the belief that the underlying file system is the best judge File systems today implement a limited set of when it comes to operations with files. Unfor- abstractions and semantics wherein applications tunately, the latter isn’t true, since applications don’t really have much of a say. The generality know more about their behavior and what they of these abstractions tends to curb the application need or do not need from the file system. Cur- performance. In the global world we live in, it seems rently, there is no real mechanism that allows reasonable that applications are treated as first-class the applications to communicate this informa- citizens by the file system layer. tion to the file system and thus have some degree In this project, we take a first step towards that goal of control over the file system functionality. by leveraging promises that applications make to the file system. The promises are then utilized to deliver For example, an application that never ap- a better-tuned and more application-oriented file pends to any of the files it creates has no means system. A very simple promise, called unique-create of conveying this information to the file sys- was implemented, wherein the application vows tem. Most file systems inherently assume that never to create a file with an existing name (in a it is good to preallocate extra blocks to a file, directory) which is then used by the file system so that when it expands, the preallocated blocks to speedup creation time.
    [Show full text]
  • Table of Contents
    TABLE OF CONTENTS Chapter 1 Introduction ............................................................................................. 3 Chapter 2 Examples for FPGA ................................................................................. 4 2.1 Factory Default Code ................................................................................................................................. 4 2.2 Nios II Control for Programmable PLL/ Temperature/ Power/ 9-axis ....................................................... 6 2.3 Nios DDR4 SDRAM Test ........................................................................................................................ 12 2.4 RTL DDR4 SDRAM Test ......................................................................................................................... 14 2.5 USB Type-C DisplayPort Alternate Mode ............................................................................................... 15 2.6 USB Type-C FX3 Loopback .................................................................................................................... 17 2.7 HDMI TX and RX in 4K Resolution ........................................................................................................ 21 2.8 HDMI TX in 4K Resolution ..................................................................................................................... 26 2.9 Low Latency Ethernet 10G MAC Demo .................................................................................................. 29 2.10 Socket
    [Show full text]
  • File Systems and Storage
    FILE SYSTEMS AND STORAGE On Making GPFS Truly General DEAN HILDEBRAND AND FRANK SCHMUCK Dean Hildebrand manages the PFS (also called IBM Spectrum Scale) began as a research project Cloud Storage Software team that quickly found its groove supporting high performance comput- at the IBM Almaden Research ing (HPC) applications [1, 2]. Over the last 15 years, GPFS branched Center and is a recognized G expert in the field of distributed out to embrace general file-serving workloads while maintaining its original and parallel file systems. He pioneered pNFS, distributed design. This article gives a brief overview of the origins of numer- demonstrating the feasibility of providing ous features that we and many others at IBM have implemented to make standard and scalable access to any file GPFS a truly general file system. system. He received a BSc degree in computer science from the University of British Columbia Early Days in 1998 and a PhD in computer science from Following its origins as a project focused on high-performance lossless streaming of multi- the University of Michigan in 2007. media video files, GPFS was soon enhanced to support high performance computing (HPC) [email protected] applications, to become the “General Parallel File System.” One of its first large deployments was on ASCI White in 2002—at the time, the fastest supercomputer in the world. This HPC- Frank Schmuck joined IBM focused architecture is described in more detail in a 2002 FAST paper [3], but from the outset Research in 1988 after receiving an important design goal was to support general workloads through a standard POSIX inter- a PhD in computer science face—and live up to the “General” term in the name.
    [Show full text]
  • Filesystems HOWTO Filesystems HOWTO Table of Contents Filesystems HOWTO
    Filesystems HOWTO Filesystems HOWTO Table of Contents Filesystems HOWTO..........................................................................................................................................1 Martin Hinner < [email protected]>, http://martin.hinner.info............................................................1 1. Introduction..........................................................................................................................................1 2. Volumes...............................................................................................................................................1 3. DOS FAT 12/16/32, VFAT.................................................................................................................2 4. High Performance FileSystem (HPFS)................................................................................................2 5. New Technology FileSystem (NTFS).................................................................................................2 6. Extended filesystems (Ext, Ext2, Ext3)...............................................................................................2 7. Macintosh Hierarchical Filesystem − HFS..........................................................................................3 8. ISO 9660 − CD−ROM filesystem.......................................................................................................3 9. Other filesystems.................................................................................................................................3
    [Show full text]
  • Hitachi Virtual Storage Platform G200, G400, G600 Service Processor Technical Reference
    Hitachi Virtual Storage Platform G200, G400, G600 Service Processor Technical Reference FE-94HM8036-00 © 2015 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd. Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. This document contains the most current information available at the time of publication. When new or revised information becomes available, this entire document will be updated and distributed to all registered users. Some of the features described in this document might not be currently available. Refer to the most recent product announcement for information about feature and product availability, or contact Hitachi Data Systems Corporation at https://portal.hds.com. Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions of the applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products is governed by the terms of your agreements with Hitachi Data Systems Corporation. By using this software, you agree that you are responsible for: a) Acquiring the relevant consents as may be required under local privacy laws or otherwise from employees and other individuals to access relevant data; and b) Verifying that data continues to be held, retrieved, deleted, or otherwise processed in accordance with relevant laws. Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries.
    [Show full text]
  • IPC: Mmap and Pipes
    Interprocess Communication: Memory mapped files and pipes CS 241 April 4, 2014 University of Illinois 1 Shared Memory Private Private address OS address address space space space Shared Process A segment Process B Processes request the segment OS maintains the segment Processes can attach/detach the segment 2 Shared Memory Private Private Private address address space OS address address space space space Shared Process A segment Process B Can mark segment for deletion on last detach 3 Shared Memory example /* make the key: */ if ((key = ftok(”shmdemo.c", 'R')) == -1) { perror("ftok"); exit(1); } /* connect to (and possibly create) the segment: */ if ((shmid = shmget(key, SHM_SIZE, 0644 | IPC_CREAT)) == -1) { perror("shmget"); exit(1); } /* attach to the segment to get a pointer to it: */ data = shmat(shmid, (void *)0, 0); if (data == (char *)(-1)) { perror("shmat"); exit(1); } 4 Shared Memory example /* read or modify the segment, based on the command line: */ if (argc == 2) { printf("writing to segment: \"%s\"\n", argv[1]); strncpy(data, argv[1], SHM_SIZE); } else printf("segment contains: \"%s\"\n", data); /* detach from the segment: */ if (shmdt(data) == -1) { perror("shmdt"); exit(1); } return 0; } Run demo 5 Memory Mapped Files Memory-mapped file I/O • Map a disk block to a page in memory • Allows file I/O to be treated as routine memory access Use • File is initially read using demand paging ! i.e., loaded from disk to memory only at the moment it’s needed • When needed, a page-sized portion of the file is read from the file system
    [Show full text]