DOCSLIB.ORG

Emerson / Motorola / Force Computers ISCSI-1 Manual (Pdf)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Emerson / Motorola / Force Computers ISCSI-1 Manual (Pdf) Full-service, independent repair center -~ ARTISAN® with experienced engineers and technicians on staff. TECHNOLOGY GROUP ~I We buy your excess, underutilized, and idle equipment along with credit for buybacks and trade-ins. Custom engineering Your definitive source so your equipment works exactly as you specify. for quality pre-owned • Critical and expedited services • Leasing / Rentals/ Demos equipment. • In stock/ Ready-to-ship • !TAR-certified secure asset solutions Expert team I Trust guarantee I 100% satisfaction Artisan Technology Group (217) 352-9330 | [email protected] | artisantg.com All trademarks, brand names, and brands appearing herein are the property o f their respective owners. Find the Emerson / Motorola / Force Computers ISCSI-1 at our website: Click HERE • SYS68K/ISCSI-1 • USER'S MANUAL Revision No. 0 NOVEMBER 1992 FORCE COMPUTERS Inc./GmbH All Rights Reserved This document shall not be duplicated, nor its contents used for any purpose, unless expose permission has been granted. Copyright by FORCE COMPUTERS® • • • • • INTRODUCTION • • • • • This page was intentionally left blank • • • • NOTE The information in this document has been carefully checked and is believed to be entirely reliable. FORCE COMPUTERS makes no warranty of any kind with regard to the material in this document, and assumes no responsibility for any errors that may appear in this document. FORCE COMPUTERS reserves the right to make changes without notice to this, or any of its products, to improve reliability, performance or design. FORCE COMPUTERS assumes no responsibility for the use of any circuitry other than circuitry which is part of a product of FORCE COMPUTERS GmbH/Inc. • FORCE COMPUTERS does not convey to the purchaser of the product described herein any license under the patent rights of FORCE COMPUTERS GmbH/Inc. nor the rights of others. FORCE COMPUTERS Inc. FORCE COMPUTERS GmbH 3165 Winchester Blvd. Prof.-Messerschmitt-Str. 1 • Campbell, CA 95008-6557 D-8014 Neubiberg/Munich U.S.A. West Germany Phone : (408) 370-6300 Phone : (089) 608 14-0 FAX : (408) 374-1146 Telex : 524190 forc-d FAX : (089) 609 77 93 • FORCE COMPUTERS FRANCE Sarl FORCE Computers UK Ltd. 11, rue Casteja No. 1 Holly Court 92100 Boulogne 3 Tring Road France Wendover Buckinghamshire HP22 6PE England Phone : (1) 4620 37 37 Phone : (0296) 625456 Telex : 206 304 forc-f Telex : 838033 FAX : (1) 4621 35 19 FAX : (0296) 624027 • • • • • This page was intentionally left blank • • • • • Table of Contents • 1.0 General Information 1-1 1.1 Hardware Features of the SYS68K/ISCSI-1 1-3 1.2 The Hardware Functions 1-4 1.2.1 The Local 68010 CPU 1-4 1.2.2 The SCSIbus Interface 1-5 1.2.3 The Floppy Disk Interface 1-6 1.2.4 The PI/T 68230 1-6 • 1.2.5 The Dual Ported RAM 1-7 1.2.6 The VMEbus Interface 1-8 1.2.7 The Bus Interrupter Module 1-8 1.2.8 The Optional Back Panel 1-9 • 2.0 Specification of the SYS68K/ISCSI-1 2-1 3.0 Ordering Information 3-1 • List of Figures Figure 1-1: Photo of the SYS68K/ISCSI-11-2 • • • • • This page was intentionally left blank • • • • • 1.0 General Information • The SYS68K/ISCSI-1 board is a high performance intelligent SCSIbus controller board which fully supports the SCSI standard. Up to four floppy drives can be controlled locally, without using the SCSIbus. The board provides local intelligence with a 68010 CPU, 68450 DMAC, SCSI Bus Controller (SCSIBC) and Floppy Disk Controller (FDC). A 128Kbyte Dual Ported RAM (DPR) is used to store data and to interface the SYS68K/ISCSI-1 board. Highest throughput is guaranteed by using a 10MHz 68450 DMAC and the NCR 5386S SCSIBC. On a single ended SCSIbus, the board works under the powerful firmware (128Kbyte EPROM area) as initiator or as target. The SYS68K/ISCSI-1's own SCSIbus I.D. is software controlled. • Four floppy drives are fully firmware supported, and can also be accessed via the SCSIbus in the target mode. The SYS68K/ISCSI-1 contains a VMEbus Rev.C/IEEE P1014 compatible interface to communicate to the host CPUs via its 128Kbyte DPR. The access address and the Address Modifier code are jumper selectable. A Bus Interrupter Module - BIM 68153 - is installed on the board to support fully asynchronous operation with the 4 different software programmable interrupt request channels. • The firmware of the SYS68K/ISCSI-1 described in the Firmware User's Manual handles all activities to/from the SCSIbus and the floppy interface. For special applications, the source code of the firmware is optionally available. • • • 1-1 /MS I: (I 1 0 0 c 1 .=. 17 7, I _.,.- .._ .7 ,.,:,.,..t.7 •Z" --' ,-...,....., CaCI 10I ° -7'' 0° ,r I. 1 ',' , C / = - CI 1 0 , 0 .-- i 1 15 I 1 :- 1 t C.,c7...--,i,,,., rx.,4 7• CI I'0 0 :.: 05. ',- C1 C1 I,7 __....,....___. CI LO 0 1, 4 - C4 ' I;1 C 1 '' I 1 .. '-',-- LC ;: CI 1O 0 Ii ,) 4 c 1 ' 1 C 1 mz7 ,,:, CI i 0 0 i I .) 1 I c / rx..;-.:_` CI V 0 0 . ! C ! ,:. ,I allill,. e• r. ..• ....-2; a. 42 :H. ' ° 0 i,'...1';.';':".'f.".:T.'.. c,,.E. 861E' ..74F046 8618 .74.64C E513 '.';:.7.:?-3- OA Q-' r:,--3: .7 •r• t- Iz fil .1 OurG IN 8628 G, •• • I) 90NLS02E4 ,7'7 8507 " falarafil/iWiart all.11111111111111.11110 am;'. cn (-) cn 053,8 _•• -0, • CV ,354236 ©NCR/5385E I:373 215fC:1101,.. 6548Y0 C905804 00 -02 3E:0 04065 6-1085057 SrO4C5641-1' 8626A •••• (30.rordc 64351 964425642-10 -J ©NCR 0370 C254161 6-10520/ . .v!ALAYS'A 61EXT PC. 0i474L5052N7 SN741S.441-1N .... .. '714111.111111.1111. Z.Z4'd ISH41111.1111.11111111111111.11111111111111. SYSOOK- ll11:1'1'111.111t111:11111111111.11111'•illIddl PrN • :1 • • • • • • • • ▶jimozwaspierd-19A8 9 • 1.1 Hardware Features of the SYS68K/ISCSI-1 • - 68010 CPU for local control (10MHz) - 68450 DMA Controller for local transfers (10MHz) - Dual Ported 128Kbyte 0 wait state static RAM between the VMEbus and the local CPU - SCSIbus interface built with the NCR 5386S SCSIbus controller. Programmable as an initiator or target - Transfer rate via the SCSIbus up to 1.5Mbyte/s • - SHUGART compatible floppy interface with the WD1772 FDC. Up to 4 floppy drives can be controlled independent of the SCSIbus - All I/O signals available on P2 connector 4 different interrupt request signals to the VMEbus. Each channel contains a software programmable IRQ level (1 to 7) and vector - Local parallel interface for controlling and monitoring board functions • - VMEbus Rev.C/IEEE P1014 compatible interface A24:D16, D8 - Watchdog timer controlling correct functions of on-board hard and software - Status and control LEDs for monitoring local activities - High level handling firmware for communication, selftest, data caching/hashing and control • • 1-3 1.2 The Hardware Functions • The local CPU reacts on the commands and initialisation parameters within the 128Kbyte DPR. Constant program run times are • guaranteed through the special hardware logic providing zero wait state operation from the DPR, independent of the accesses from the VMEbus to the DPR. The SYS68K/ISCSI-1 consists of self-test functions as well as a hardware watchdog timer which controls the activities of the 68010 CPU running with 10MHz. User supplied programs can be loaded into the DPR and executed by the local CPU to adapt and extend board functionality. The local CPU controls the SCSIbus and the floppy disk interface via local interrupts, and communicates to the host CPU via the DPR or via interrupt request to the VMEbus, generated by a Bus Interrupter Module. • The I/O signals to be supported through the NCR 5386S are terminated on the PC board. The terminators can be removed in order to be able to connect more than 3 SCSI devices. 1.2.1 The Local 68010 CPU • A 10MHz 68010 CPU is installed on the SYS68K/ISCSI-1 to control the data traffic between the serial I/O channels and the VMEbus host CPU(s). Two EPROMs with a maximum capacity of 128Kbyte are installed on the SYS68K/ISCSI-1 to hold the handling firmware. Constant zero wait state operation from the EPROM guarantees maximum CPU throughput and a fixed program run time. The 128Kbyte Dual Ported RAM is also accessible without the • insertion of wait states by using a CPU clock synchronized arbitration mechanism. The accesses from the CPU to the DPR are not delayed if a VMEbus access is pending or being executed. A local timer, included in the PI/T, is used to interrupt the CPU for task scheduling, command interpretation and execution. The CPU and all I/O devices can be RESET through a SYSTEM reset via the SYSRESET signal of the VMEbus or by accessing a dedicated location within the DPR reserved for this function. 1-4 • • 1.2.2 The SCSIbus Interface The SYS68K/ISCSI-1 contains an NCR 5386S SCSIbus controller and an • NCR 8310 SCSIbus driver/transceiver. These chips provide the following features: - Support of the ANSI X3T9.2 SCSI standard - Asynchronous data transfer to 1.5Mbyte per second - Support of both initiator and target modes - Parity generation with optional checking - Support of arbitration - Control of all bus signals except RESET • - Doubly-buffered data register - Versatile MPU bus interface - Memory or I/O mapped MPU interface - DMA or programmed I/O transfer • - 24-bit internal transfer counter - Programmable (re)selection timeouts - Interrupt of MPU on all bus conditions requiring service - SCSI pass parity optional with checking - 48mA driver • The NCR 53865 SCSI Bus Controller communicates with the 68010 CPU and the 68450 DMAC as a peripheral device.
Load more

Recommended publications
  • Implementation of an Orthogonally Persistent L4 -Kernel Based System
    Implementation of an Orthogonally Persistent L4 -Kernel Based System Christian Ceelen ÐÒÖºÙ º Supervisor: Cand. Scient. Espen Skoglund Universitat¨ Karlsruhe 15th February 2002 2 3 Abstract Orthogonal persistent systems open up possibilities for a wide number of appli- cations. Even more, it is a very natural concept for the storage of information, since objects and information persists until the end of their lifetime. Most current commercial non-persistent systems have only an explicit storage model. Thus, an application has to care for the persistent storage of data itself. This has to be done by transforming the data structures into something that can be stored within a file. Furthermore the file has to be opened, written to and saved explicitly; a source of overhead for programmers. Moreover the programmer also has to estimate the life-time of all valuable data. Including the conversion and recovery of data, the amount of code needed to store data explicitly could easily take up a third or half of the actual programming work. In order to support a convenient system environment, persistent storage could be handled implicitly by the operating system. The operating system has to store for each task an image of the user memory and all kernel internal data like page- tables, mapping structures, file descriptors and so on. This approach is very de- manding and very error-prone for current monolithic systems. Therefore we pro- pose a -kernel based system instead. The proposed work should provide an implementation base for further persistent systems by supplying the necessary mechanisms to build persistent applications on top of the -kernel.
    [Show full text]
  • I.MX Linux® Reference Manual
    i.MX Linux® Reference Manual Document Number: IMXLXRM Rev. 1, 01/2017 i.MX Linux® Reference Manual, Rev. 1, 01/2017 2 NXP Semiconductors Contents Section number Title Page Chapter 1 About this Book 1.1 Audience....................................................................................................................................................................... 27 1.1.1 Conventions................................................................................................................................................... 27 1.1.2 Definitions, Acronyms, and Abbreviations....................................................................................................27 Chapter 2 Introduction 2.1 Overview.......................................................................................................................................................................31 2.1.1 Software Base................................................................................................................................................ 31 2.1.2 Features.......................................................................................................................................................... 31 Chapter 3 Machine-Specific Layer (MSL) 3.1 Introduction...................................................................................................................................................................37 3.2 Interrupts (Operation)..................................................................................................................................................
    [Show full text]
  • Chapter 1. Origins of Mac OS X
    1 Chapter 1. Origins of Mac OS X "Most ideas come from previous ideas." Alan Curtis Kay The Mac OS X operating system represents a rather successful coming together of paradigms, ideologies, and technologies that have often resisted each other in the past. A good example is the cordial relationship that exists between the command-line and graphical interfaces in Mac OS X. The system is a result of the trials and tribulations of Apple and NeXT, as well as their user and developer communities. Mac OS X exemplifies how a capable system can result from the direct or indirect efforts of corporations, academic and research communities, the Open Source and Free Software movements, and, of course, individuals. Apple has been around since 1976, and many accounts of its history have been told. If the story of Apple as a company is fascinating, so is the technical history of Apple's operating systems. In this chapter,[1] we will trace the history of Mac OS X, discussing several technologies whose confluence eventually led to the modern-day Apple operating system. [1] This book's accompanying web site (www.osxbook.com) provides a more detailed technical history of all of Apple's operating systems. 1 2 2 1 1.1. Apple's Quest for the[2] Operating System [2] Whereas the word "the" is used here to designate prominence and desirability, it is an interesting coincidence that "THE" was the name of a multiprogramming system described by Edsger W. Dijkstra in a 1968 paper. It was March 1988. The Macintosh had been around for four years.
    [Show full text]
  • Hypervisor-Based Active Data Protection for Integrity And
    The 13th Annual ADFSL Conference on Digital Forensics, Security and Law, 2018 HYPERVISOR-BASED ACTIVE DATA PROTECTION FOR INTEGRITY AND CONFIDENTIALITY OF DYNAMICALLY ALLOCATED MEMORY IN WINDOWS KERNEL Igor Korkin, PhD Security Researcher Moscow, Russia [email protected] ABSTRACT One of the main issues in the OS security is providing trusted code execution in an untrusted environment. During executing, kernel-mode drivers dynamically allocate memory to store and process their data: Windows core kernel structures, users’ private information, and sensitive data of third-party drivers. All this data can be tampered with by kernel-mode malware. Attacks on Windows-based computers can cause not just hiding a malware driver, process privilege escalation, and stealing private data but also failures of industrial CNC machines. Windows built-in security and existing approaches do not provide the integrity and confidentiality of the allocated memory of third-party drivers. The proposed hypervisor-based system (AllMemPro) protects allocated data from being modified or stolen. AllMemPro prevents access to even 1 byte of allocated data, adapts for newly allocated memory in real time, and protects the driver without its source code. AllMemPro works well on newest Windows 10 1709 x64. Keywords: hypervisor-based protection, Windows kernel, Intel, CNC security, rootkits, dynamic data protection. 1. INTRODUCTION The vulnerable VirtualBox driver (VBoxDrv.sys) Currently, protection of data in computer memory has been exploited by Turla rootkit and allows to is becoming essential. Growing integration of write arbitrary values to any kernel memory (Singh, ubiquitous Windows-based computers into 2015; Kirda, 2015). industrial automation makes this security issue critically important.
    [Show full text]
  • Cpre 488 – Embedded Systems Design
    CprE 488 – Embedded Systems Design MP-3: Embedded Linux Assigned: Monday of Week 8 Due: Monday of Week 10 Points: 100 + bonus for target recognition capabilities [Note: to this point in the semester we have been writing bare metal code, i.e. applications without anything more than the most basic system software (“standalone” mode in Xilinx terms). While this comes with several advantages due to its simplicity, it is fairly common for embedded systems to run an Operating System (OS). As the complexities of an OS are significant enough to merit their own course, in this class we are focusing more on practical aspects of porting an OS (Linux) to an (ARM-based) embedded system. Specifically, the goal of this Machine Problem is for your group to gain familiarity with three different aspects of embedded system design: 1. Linux bring up – you will work through the stages of configuring, compiling, and booting for an open source Linux kernel targeting the Xilinx ZedBoard. 2. Linux driver development – you will adapt a template to develop a driver for a USB-powered missile launcher. 3. Linux system programming – you will write applications that target conventional Linux device drivers.] 1) Your Mission. It was bound to happen sooner or later. I am of course speaking of an alien invasion. Having already laid waste to the 100 most populous cities in the United States, the aliens have moved on to central Iowa. Holed up in Coover Hall, you and your friends have miraculously discovered the aliens’ hidden weakness: foam-tipped darts! It’s arguably no less plausible than the plot of Independence Day or even Signs.
    [Show full text]
  • Setup Guide for the 610, 620, and 650
    Oracle® MICROS Workstation 6 Series Setup Guide for the 610, 620, and 650 E73098-20 March 2020 Oracle MICROS Workstation 6 Series Setup Guide for the 610, 620, and 650, E73098-20 Copyright © 2015, 2020, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • Infoprint Processdirector V2.2.1 and Infoprint 5000 Ink Suite Announcement Overview
    CRD #SW11-1418-1 IPPD V2.2.1 Ink Suite Announcement Announcement: June 17, 2011 InfoPrint ProcessDirector V2.2.1 and InfoPrint 5000 Ink Suite Announcement Overview InfoPrint ProcessDirector is an extensible, configurable output process management system that lets you start small and grow over time. With core capabilities plus optional add-on features, InfoPrint ProcessDirector allows flexible control of your print and mail production processes. It can streamline operations, improve process integrity, enhance operator productivity, reduce errors and help lower costs. InfoPrint ProcessDirector is also the backbone software of InfoPrint Automated Document Factory solutions: Mailroom Integrity, Postal Optimization and Output Management. This release of InfoPrint ProcessDirector focuses on integration of the InfoPrint 5000 Ink Suite of tools – which provide cost savings and quality improvements for files that are printed on the InfoPrint 5000. With InfoPrint ProcessDirector, you can meet production commitments and adapt to unexpected changes without adding staff, shifts or equipment. Instead, move jobs easily across multi-vendor machines, datastreams and sites to improve asset utilization. Boost productivity with the capability to: Drive printers and inserters more efficiently Avoid missing deadlines and service level agreements Bring in new types of work Be prepared for unexpected disasters Integrate with other business systems Highlights Integration with Ink Savvy, a software tool that can optimize a print file to improve color quality and use less ink when printing to the InfoPrint 5000. Ink Estimation feature, which allows you to process a file and get an estimated cost of ink for printing the file on the InfoPrint 5000 with a 10% margin of error.
    [Show full text]
  • The Linux SCSI Programming HOWTO the Linux SCSI Programming HOWTO
    The Linux SCSI programming HOWTO The Linux SCSI programming HOWTO Table of Contents The Linux SCSI programming HOWTO.........................................................................................................1 Heiko Eißfeldt heiko@colossus.escape.de..............................................................................................1 1.What's New?.........................................................................................................................................1 2.Introduction...........................................................................................................................................1 3.What Is The Generic SCSI Interface?...................................................................................................1 4.What Are The Requirements To Use It?...............................................................................................1 5.Programmers Guide .............................................................................................................................1 6.Overview Of Device Programming......................................................................................................1 7.Opening The Device.............................................................................................................................1 8.The Header Structure............................................................................................................................2 9.Inquiry Command Example..................................................................................................................2
    [Show full text]
  • Popcorn Linux: Enabling Efficient Inter-Core Communication in a Linux-Based Multikernel Operating System
    Popcorn Linux: enabling efficient inter-core communication in a Linux-based multikernel operating system Benjamin H. Shelton Thesis submitted to the Faculty of the Virginia Polytechnic Institute and State University in partial fulfillment of the requirements for the degree of Master of Science in Computer Engineering Binoy Ravindran Christopher Jules White Paul E. Plassman May 2, 2013 Blacksburg, Virginia Keywords: Operating systems, multikernel, high-performance computing, heterogeneous computing, multicore, scalability, message passing Copyright 2013, Benjamin H. Shelton Popcorn Linux: enabling efficient inter-core communication in a Linux-based multikernel operating system Benjamin H. Shelton (ABSTRACT) As manufacturers introduce new machines with more cores, more NUMA-like architectures, and more tightly integrated heterogeneous processors, the traditional abstraction of a mono- lithic OS running on a SMP system is encountering new challenges. One proposed path forward is the multikernel operating system. Previous efforts have shown promising results both in scalability and in support for heterogeneity. However, one effort’s source code is not freely available (FOS), and the other effort is not self-hosting and does not support a majority of existing applications (Barrelfish). In this thesis, we present Popcorn, a Linux-based multikernel operating system. While Popcorn was a group effort, the boot layer code and the memory partitioning code are the authors work, and we present them in detail here. To our knowledge, we are the first to support multiple instances of the Linux kernel on a 64-bit x86 machine and to support more than 4 kernels running simultaneously. We demonstrate that existing subsystems within Linux can be leveraged to meet the design goals of a multikernel OS.
    [Show full text]
  • 101 Ways to Save Apple by James Daly
    http://www.wired.com/wired/archive/5.06/apple_pr.html 101 Ways to Save Apple By James Daly An assessment of what can be done to fix a once-great company. Dear Apple, In the movie Independence Day, a PowerBook saves the earth from destruction. Now it's time to return the favor. Unfortunately, even devoted Mac addicts must admit that you look a little beleaguered these days: a confusing product line, little inspiration from the top, software developers fleeing. But who wants to live in a world without you? Not us. So we surveyed a cross section of hardcore Mac fans and came up with 101 ways to get you back on the path to salvation. We chose not to resort to time travel or regurgitate the same old shoulda/coulda/wouldas (you shoulda licensed your OS in 1987, for instance, or coulda upped your price/performance in 1993). We don't believe Apple is rotten to the core. Chrysler nearly went under in the late 1970s and came back to lead its industry. Here's a fresh assessment of what can be done to fix your once-great company using the material at hand. Don't wait for a miracle. You have the power to save the world - and yourself. Edited by James Daly 1. Admit it. You're out of the hardware game. Outsource your hardware production, or scrap it entirely, to compete more directly with Microsoft without the liability of manufacturing boxes. 2. License the Apple name/technology to appliance manufacturers and build GUIs for every possible device - from washing machines to telephones to WebTV.
    [Show full text]
  • Ceph Parallel File System Evaluation Report
    ORNL/TM-2013/151 National Center for Computatational Sciences Ceph Parallel File System Evaluation Report Feiyi Wang Mark Nelson ORNL/NCCS Inktank Inc. Other contributors: Sarp Oral Doug Fuller Scott Atchley Blake Caldwell James Simmons Brad Settlemyer Jason Hill Sage Weil (Inktank Inc.) Prepared by OAK RIDGE NATIONAL LABORATORY Oak Ridge, Tennessee 37831-6283 managed by UT-BATTELLE, LLC for the U.S. DEPARTMENT OF ENERGY This research was supported by, and used the resources of, the Oak Ridge Leadership Computing Facility, located in the National Center for Computational Sciences at ORNL, which is managed by UT Battelle, LLC for the U.S. DOE (under the contract No. DE-AC05-00OR22725). Contents 1 Introduction 1 2 Testbed Environment Description 2 3 Baseline Performance 3 3.1 Block I/O over Native IB ..................................... 3 3.2 IP over IB ............................................. 3 4 System Tuning 3 5 XFS Performance As Backend File System 4 6 Ceph RADOS Scaling: Initial Test 5 6.1 Scaling on number of OSDs per server ............................ 6 6.2 Scaling on number of OSD servers ............................... 6 7 Ceph File System Performance: Initial Test 7 8 Improving RADOS Performance 8 8.1 Disable Cache Mirroring on Controllers ............................ 9 8.2 Disable TCP autotuning ..................................... 10 8.3 Repeating RADOS Scaling Test ................................. 10 9 Improving Ceph File System Performance 12 9.1 Disabling Client CRC32 ..................................... 12 9.2 Improving IOR Read Performance ............................... 13 9.3 Repeating the IOR Scaling Test ................................. 14 10 Metadata Performance 15 11 Observations and Conclusions 17 Appendix A - CephFS Final Mount 18 Appendix B - OSD File System Options 18 Appendix C - CRUSH map 19 Appendix D - Final ceph.conf 23 Appendix E - Tuning Parameters 24 3 List of Figures 1 DDN SFA10K hardware and host connection diagram ...................
    [Show full text]
  • Administration Guide Administration Guide SUSE Linux Enterprise Server 15 SP1
    SUSE Linux Enterprise Server 15 SP1 Administration Guide Administration Guide SUSE Linux Enterprise Server 15 SP1 Covers system administration tasks like maintaining, monitoring and customizing an initially installed system. 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 About This Guide xxii 1 Available Documentation xxiii 2 Giving Feedback xxv 3 Documentation Conventions xxv 4 Product Life Cycle and Support xxvii Support Statement for SUSE Linux Enterprise Server xxviii • Technology Previews xxix I COMMON TASKS 1 1 Bash and Bash
    [Show full text]