DOCSLIB.ORG

On the Implementation and Evaluation of Berkeley Sockets on Maestro2 Cluster Computing Environment

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
On the Implementation and Evaluation of Berkeley Sockets on Maestro2 Cluster Computing Environment On the Implementation and Evaluation of Berkeley Sockets on Maestro2 cluster computing environment ½ ½¾ Ricardo Guapo½¾ , Shinichi Yamagiwa and Leonel Sousa ½ INESC-ID, Rua Alves Redol 9 Apartado 13069, 1000-029 Lisboa Portugal ¾ Instituto Superior Tecnico´ - Av. Rovisco Pais, 1049-001 Lisboa Portugal guapo, yama, las @sips.inesc-id.pt Abstract tocol layers. Thus, those communication software are able to achieve almost 100% of the potential network hardware The support on cluster environments of ”legacy proto- performance. cols” is important to avoid rewriting the code of applica- To take advantage of such high performance protocols, tions, but this support should not prevent to achieve the the applications need to use those proprietary communica- maximum communication performance. This paper ad- tion software. Once the necessity to change the platform dresses this issue by implementing the Berkeley sockets in- of the applications, namely to a different cluster, a serious terface over the MMP message passing protocol, which is problem arises to keep the compatibility of the code, namely the lower layer of the Maestro2 cluster communication net- in what respect communication. Therefore, it is necessary work. Experimental results show that MMP-Sockets offers for the programmer to rearrange the communication part of a minimum latency of 25s and a maximum throughput of the applications regarding to the new dedicated communi- 1250Mbps. These values correspond to a relative increase cation software. of 80% for the latency and a decrease of about 30% for the To address this portability/compatibility problem of ap- throughput, regarding to a communication based only on plications on different cluster hardware, the MPI standard MMP. However, MMP-Sockets increases the compatibility was proposed [9]. MPI defines a standard API for a message and portability of developed applications. passing library. It is suitable for parallel applications for which the communication size and timing are defined stati- cally, such as: matrix computation, Fast Fourier Transform 1. Introduction (FFT) and a LU decomposition. However, not all high per- formance communication demanding programs have pre- Performance extracted from off-the-shelf components cise knowledge about the amount data transfers, e.g.: HTTP is the key to design efficient commodity cluster comput- based video transcoding [6] and large data-bases. ers. For the parallel application in clusters, it is important Even if ported to MPI, those kind of applications still to reduce the overheads in the network hardware such as require the use of a TCP connection to clients outside the the copy operations between user application and drivers cluster. This forces the existence of two communication buffers and also the excessive TCP information headers for methods/libraries, TCP and MPI, to be conjugated together, local communication. which can be avoided if TCP would already be present at To achieve the potential network performance of clus- high performance for inside cluster communication as the ter computers hardware, dedicated software is applied for standard unified protocol. Therefore, it has been recently implementing the communication interface among applica- started an effort to bring cluster high performance com- tion’s parallel processes. An example of such specific net- munication to applications using TCP, by implementing li- works is the Myrinet [10] network hardware and its dedi- braries which will enable the execution of those applications cated low-level protocols GM [1], PM [4] and BIP [8]. GM, in clusters [3]. PM and BIP optimize the communication with Myrinet net- This paper is focused on the design and implementation work hardware and implement the zero-copy network inter- of a fully compatible communication library of TCP over face, by touching the user memory space that is locked by a dedicated communication software that can achieve high the OS (pindowned) directly to send and receive messages. performance communication for cluster computing. For Those protocols touch the hardware directly from the user that, the Berkeley sockets interface was implemented over application to bypass the thick conventional network pro- the MMP message passing protocol, which is the lower Host layer of the Maestro2 cluster communication environment. Host Memory Moreover, we will discuss the variation in the communica- Space tion performance with the change of the parameters in our User 1) Space socket implementation. Fill m Pindowned Host CPU essage The paper is organized as follows: the next section Buffer presents an overview of the high performance network tech- Issue Complete request notification nology Maestro2, with the dedicated communication soft- 2) 5) 3) Transmission DMA ware called MMP. Section 3 presents the design and imple- Buffer transfer mentation of the Berkeley sockets API over the MMP com- Network munication library. Section 4 presents experimental results Interface CPU 4) and evaluate the relative performance of the new developed Physical Switch Box library. Section 4 finally concludes this paper. transmission PCI Interface 2. Background Figure 1. Maestro network diagram and send The Maestro2 network [11][12] is an intelligent network operation subactions that has been developed to address the overheads of inter- cluster communication. The Maestro network is supported generates and writes requests to the switch controller. by a dedicated communication protocol, implemented as a message passing library, called MMP. Maestro2 Message Passing protocol: To achieve high Maestro2 network: The Maestro2 network is composed performance with Maestro2 PC clusters, the low latency by network interfaces (NI) and a Switch Box (SB) as and high bandwidth dedicated communication MMP library shown in the diagram of figure 1. Each network interface was developed. MMP consists of a user level library and the is connected via two Low Voltage Differential Signalling Maestro2 communication firmware that directly controls NI (LVDS) [5] cables for transmission and reception, and is and SB. The two main key observations in developing MMP connected to a commodity computer such as a personal were: i) to avoid unnecessary overhead so that the commu- computer or a WorkStation via a 64bit@66MHz PCI bus. nication does not degrade the overall performance of the The connection between NI and SB is full-duplex and the parallel applications; ii) in accessing the CPU, computation peak bandwidth is of 3.2Gbps. Currently, the SB has ports must have higher priority than communication. to directly connect up to eight NI(s). One or more ports Regarding the first issue, MMP implements the zero- can increase the fan-out of the switch by cascading SB(s). copy mechanism on Linux OS (Operating System), elimi- The NI includes a NI manager, a PCI interface, network nating data copy between user and kernel memory spaces FIFO buffers, a link controller (MLC-X) and LVDS trans- and avoiding system calls. The zero-copy communication mitter/receiver. The NI manager works as a processor ele- technique consists on exchanging messages between the ment in charge of handling communications, and consists of sender’s application memory space to the receiver’s one di- a PowerPC603e@300MHz and 64Mbyte of SDRAM. The rectly, by using DMA operations between network hard- PCI interface maps the address space of the SDRAM and ware buffers and application buffers that are allocated and part of host processor’s memory into the PowerPC’s address locked [7] (generally called, pindowned). space. A 8Kbyte network FIFO buffers to store incom- To deal with the second issue, MMP communication ing and outgoing messages. The MLC-X is a full duplex functions were made to be non-blocking. In addition, com- link layer controller on which the continuous network burst plex communication operations, such as the creation of transfer is implemented. MLC-X supports two communi- data chunks, migrates to the physical network. There- cation channels between the network FIFO buffers. And fi- fore, the communication code will be overlapped with the nally, LVDS transmitter/receiver drive its physical medium computation code on the host processor. MMP provides under control of MLC-X. It transmits and receives data via primitive message-based non-blocking communication in- its 3.2 Gbps full duplex link. The PCI interface, network terface functions (MMP send(), MMP Recv()), and cor- buffers, and MLC-X are implemented into the Virtex-II responding request completion synchronization functions FPGA (Field Programmable Gate Array) chip [13]. The MMP send wait(), MMP recv wait(). SB consists of four SB interfaces, a SB manager and a MMP uses a connection-less data transmission sys- switch controller. Each SB interface manages two ports tem based on messages, similar to UDP. Arguments for and includes a message analyzer. The message analyzer ex- the sending or receiving functions indicate only the re- tracts the message headers of each incoming message, and ceiver and sender end-point identification, besides mes- passes it to the SB manager. The SB manager consists of a sage identification parameters. When an application call PowerPC603e, 32Mbyte SDRAM, and a routing circuit that MMP Initialize() function, MMP will provide an in- dividual ”port” to identify the application end-point in the User ApplicationApplication MMP network. In figure 1 it is presented the sub-actions Applic ation Reception D a ta Bu ffe r s wait queue performed by a MMP send operation: 1) application creates Berkeley Interface the message in the pindowned memory; 2) it notifies the send request; 3) MMP firmware in NI issues DMA transfers Core Data Str uc tur e Connection information: between main memory and network buffers; 4) the message File descriptors MMP Endpoint is transmitted by link-layer to SB and 5) the request status Connection state Core Engine is updated to completed. MMP Transmission It was on top of MMP library that the Berkeley socket Buffer s MMP Automation Communication interface was implemented in this work. Next section will Layer Protocols be focused on the implementation aspects. MMP TCP 3.
Load more

Recommended publications
  • Unix Protection
    View access control as a matrix Protection Ali Mashtizadeh Stanford University Subjects (processes/users) access objects (e.g., files) • Each cell of matrix has allowed permissions • 1 / 39 2 / 39 Specifying policy Two ways to slice the matrix Manually filling out matrix would be tedious • Use tools such as groups or role-based access control: • Along columns: • - Kernel stores list of who can access object along with object - Most systems you’ve used probably do this dir 1 - Examples: Unix file permissions, Access Control Lists (ACLs) Along rows: • dir 2 - Capability systems do this - More on these later. dir 3 3 / 39 4 / 39 Outline Example: Unix protection Each process has a User ID & one or more group IDs • System stores with each file: • 1 Unix protection - User who owns the file and group file is in - Permissions for user, any one in file group, and other Shown by output of ls -l command: 2 Unix security holes • user group other owner group - rw- rw- r-- dm cs140 ... index.html 3 Capability-based protection - Eachz}|{ groupz}|{ z}|{ of threez}|{ lettersz }| { specifies a subset of read, write, and execute permissions - User permissions apply to processes with same user ID - Else, group permissions apply to processes in same group - Else, other permissions apply 5 / 39 6 / 39 Unix continued Non-file permissions in Unix Directories have permission bits, too • Many devices show up in file system • - Need write permission on a directory to create or delete a file - E.g., /dev/tty1 permissions just like for files Special user root (UID 0) has all
    [Show full text]
  • A Practical UNIX Capability System
    A Practical UNIX Capability System Adam Langley <[email protected]> 22nd June 2005 ii Abstract This report seeks to document the development of a capability security system based on a Linux kernel and to follow through the implications of such a system. After defining terms, several other capability systems are discussed and found to be excellent, but to have too high a barrier to entry. This motivates the development of the above system. The capability system decomposes traditionally monolithic applications into a number of communicating actors, each of which is a separate process. Actors may only communicate using the capabilities given to them and so the impact of a vulnerability in a given actor can be reasoned about. This design pattern is demonstrated to be advantageous in terms of security, comprehensibility and mod- ularity and with an acceptable performance penality. From this, following through a few of the further avenues which present themselves is the two hours traffic of our stage. Acknowledgments I would like to thank my supervisor, Dr Kelly, for all the time he has put into cajoling and persuading me that the rest of the world might have a trick or two worth learning. Also, I’d like to thank Bryce Wilcox-O’Hearn for introducing me to capabilities many years ago. Contents 1 Introduction 1 2 Terms 3 2.1 POSIX ‘Capabilities’ . 3 2.2 Password Capabilities . 4 3 Motivations 7 3.1 Ambient Authority . 7 3.2 Confused Deputy . 8 3.3 Pervasive Testing . 8 3.4 Clear Auditing of Vulnerabilities . 9 3.5 Easy Configurability .
    [Show full text]
  • System Calls System Calls
    System calls We will investigate several issues related to system calls. Read chapter 12 of the book Linux system call categories file management process management error handling note that these categories are loosely defined and much is behind included, e.g. communication. Why? 1 System calls File management system call hierarchy you may not see some topics as part of “file management”, e.g., sockets 2 System calls Process management system call hierarchy 3 System calls Error handling hierarchy 4 Error Handling Anything can fail! System calls are no exception Try to read a file that does not exist! Error number: errno every process contains a global variable errno errno is set to 0 when process is created when error occurs errno is set to a specific code associated with the error cause trying to open file that does not exist sets errno to 2 5 Error Handling error constants are defined in errno.h here are the first few of errno.h on OS X 10.6.4 #define EPERM 1 /* Operation not permitted */ #define ENOENT 2 /* No such file or directory */ #define ESRCH 3 /* No such process */ #define EINTR 4 /* Interrupted system call */ #define EIO 5 /* Input/output error */ #define ENXIO 6 /* Device not configured */ #define E2BIG 7 /* Argument list too long */ #define ENOEXEC 8 /* Exec format error */ #define EBADF 9 /* Bad file descriptor */ #define ECHILD 10 /* No child processes */ #define EDEADLK 11 /* Resource deadlock avoided */ 6 Error Handling common mistake for displaying errno from Linux errno man page: 7 Error Handling Description of the perror () system call.
    [Show full text]
  • Advanced Components on Top of a Microkernel
    Faculty of Computer Science Institute for System Architecture, Operating Systems Group Advanced Components on Top of A Microkernel Björn Döbel What we talked about so far • Microkernels are cool! • Fiasco.OC provides fundamental mechanisms: – Tasks (address spaces) • Container of resources – Threads • Units of execution – Inter-Process Communication • Exchange Data • Timeouts • Mapping of resources TU Dresden, 2012-07-24 L4Re: Advanced Components Slide 2 / 54 Lecture Outline • Building a real system on top of Fiasco.OC • Reusing legacy libraries – POSIX C library • Device Drivers in user space – Accessing hardware resources – Reusing Linux device drivers • OS virtualization on top of L4Re TU Dresden, 2012-07-24 L4Re: Advanced Components Slide 3 / 54 Reusing Existing Software • Often used term: legacy software • Why? – Convenience: • Users get their “favorite” application on the new OS – Effort: • Rewriting everything from scratch takes a lot of time • But: maintaining ported software and adaptions also does not come for free TU Dresden, 2012-07-24 L4Re: Advanced Components Slide 4 / 54 Reusing Existing Software • How? – Porting: • Adapt existing software to use L4Re/Fiasco.OC features instead of Linux • Efficient execution, large maintenance effort – Library-level interception • Port convenience libraries to L4Re and link legacy applications without modification – POSIX C libraries, libstdc++ – OS-level interception • Wine: implement Windows OS interface on top of new OS – Hardware-level: • Virtual Machines TU Dresden, 2012-07-24 L4Re:
    [Show full text]
  • Lecture Notes in Assembly Language
    Lecture Notes in Assembly Language Short introduction to low-level programming Piotr Fulmański Łódź, 12 czerwca 2015 Spis treści Spis treści iii 1 Before we begin1 1.1 Simple assembler.................................... 1 1.1.1 Excercise 1 ................................... 2 1.1.2 Excercise 2 ................................... 3 1.1.3 Excercise 3 ................................... 3 1.1.4 Excercise 4 ................................... 5 1.1.5 Excercise 5 ................................... 6 1.2 Improvements, part I: addressing........................... 8 1.2.1 Excercise 6 ................................... 11 1.3 Improvements, part II: indirect addressing...................... 11 1.4 Improvements, part III: labels............................. 18 1.4.1 Excercise 7: find substring in a string .................... 19 1.4.2 Excercise 8: improved polynomial....................... 21 1.5 Improvements, part IV: flag register ......................... 23 1.6 Improvements, part V: the stack ........................... 24 1.6.1 Excercise 12................................... 26 1.7 Improvements, part VI – function stack frame.................... 29 1.8 Finall excercises..................................... 34 1.8.1 Excercise 13................................... 34 1.8.2 Excercise 14................................... 34 1.8.3 Excercise 15................................... 34 1.8.4 Excercise 16................................... 34 iii iv SPIS TREŚCI 1.8.5 Excercise 17................................... 34 2 First program 37 2.1 Compiling,
    [Show full text]
  • Operating System Support for Parallel Processes
    Operating System Support for Parallel Processes Barret Rhoden Electrical Engineering and Computer Sciences University of California at Berkeley Technical Report No. UCB/EECS-2014-223 http://www.eecs.berkeley.edu/Pubs/TechRpts/2014/EECS-2014-223.html December 18, 2014 Copyright © 2014, by the author(s). All rights reserved. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission. Operating System Support for Parallel Processes by Barret Joseph Rhoden A dissertation submitted in partial satisfaction of the requirements for the degree of Doctor of Philosophy in Computer Science in the Graduate Division of the University of California, Berkeley Committee in charge: Professor Eric Brewer, Chair Professor Krste Asanovi´c Professor David Culler Professor John Chuang Fall 2014 Operating System Support for Parallel Processes Copyright 2014 by Barret Joseph Rhoden 1 Abstract Operating System Support for Parallel Processes by Barret Joseph Rhoden Doctor of Philosophy in Computer Science University of California, Berkeley Professor Eric Brewer, Chair High-performance, parallel programs want uninterrupted access to physical resources. This characterization is true not only for traditional scientific computing, but also for high- priority data center applications that run on parallel processors. These applications require high, predictable performance and low latency, and they are important enough to warrant engineering effort at all levels of the software stack.
    [Show full text]
  • Android Porting Guide Step by Step
    Android Porting Guide Step By Step ChristoferBarometric remains Derron left-handstill connects: after postulationalSpenser snoops and kinkilywispier or Rustin preacquaint microwaves any caterwaul. quite menacingly Hewie graze but intubated connectedly. her visionaries hereditarily. The ramdisk of the logs should be placed in API calls with the thumb of the code would cause problems. ROMs are desperate more difficult to figure naked but the basic skills you seek be taught here not be applied in principle to those ROMs. Find what catch the prescribed procedures to retrieve taken. Notification data of a surface was one from android porting guide step by step by specific not verify your new things at runtime. Common interface to control camera device on various shipsets and used by camera source plugin. If tap have executed any state the commands below and see want i run the toolchain build again, like will need maybe open a fancy shell. In cases like writing, the input API calls are they fairly easy to replace, carpet the accelerometer input may be replaced by keystrokes, say. Sometimes replacing works and some times editing. These cookies do not except any personally identifiable information. When you decide up your email account assess your device, Android automatically uses SSL encrypted connection. No custom ROM developed for team yet. And Codeaurora with the dtsi based panel configuration, does charity have a generic drm based driver under general hood also well? Means describe a lolipop kernel anyone can port Marshmallow ROMs? Fi and these a rain boot. After flashing protocol. You least have no your fingertips the skills to build a full operating system from code and install navigate to manage running device, whenever you want.
    [Show full text]
  • A Component-Based Environment for Android Apps
    A Component-based Environment for Android Apps Alexander Senier FOSDEM, Brussels, 2020-02-02 Smartphone Trust Challenges Privilege Escalation 2020-02-02 2 Media Frameworks are not getting simpler. How do we avoid such fatal errors? 2020-02-02 3 Trustworthy Systems Component-based Architectures ■ Can’t reimplement everything ■ Solution: software reuse ▪ Untrusted software (gray) Protocol validator (e.g. Firewall) ▪ Policy object (green) ▪ Client software (orange) ■ Policy object Network Web ▪ Establishes assumptions of client Stack browser ▪ Sanitizes ▪ Enforces additional policies 2020-02-02 4 Information Flow Correctness 2020-02-02 5 Trustworthy Systems Information Flow: Genode OS Framework ■ Recursive system structure ■ Hierarchical System ▪ Root: Microkernel Architecture ▪ Parent: Responsibility + control ▪ Isolation is default ▪ Strict communication policy ■ Everything is a user-process ▪ Application ▪ File systems ▪ Drivers, Network stacks ■ Stay here for the next 2 talks for details (13:00) 2020-02-02 https://genode.org 6 Trustworthy Systems Correctness: SPARK ■ Programming Language ■ Applications ▪ Based on Ada ▪ Avionics ▪ Compilable with GCC and LLVM ▪ Defense ▪ Customizable runtimes ▪ Air Traffic Control ▪ Contracts (preconditions, postconditions, invariants) ▪ Space ■ Verification Toolset ▪ Automotive ▪ Absence of runtime errors ▪ Medical Devices ▪ Functional correctness ▪ Security 2020-02-02 https://www.adacore.com/about-spark 7 Applying this Approach to Android Apps 2020-02-02 8 GART Project Objectives ■ Unmodified Android
    [Show full text]
  • Capability Myths Demolished
    Capability Myths Demolished Mark S. Miller Ka-Ping Yee Jonathan Shapiro Combex, Inc. University of California, Berkeley Johns Hopkins University [email protected] [email protected] [email protected] ABSTRACT The second and third myths state false limitations on We address three common misconceptions about what capability systems can do, and have been capability-based systems: the Equivalence Myth (access propagated by a series of research publications over the control list systems and capability systems are formally past 20 years (including [2, 3, 7, 24]). They have been equivalent), the Confinement Myth (capability systems cited as reasons to avoid adopting capability models cannot enforce confinement), and the Irrevocability and have even motivated some researchers to augment Myth (capability-based access cannot be revoked). The capability systems with extra access checks [7, 13] in Equivalence Myth obscures the benefits of capabilities attempts to fix problems that do not exist. The myths as compared to access control lists, while the Confine- about what capability systems cannot do continue to ment Myth and the Irrevocability Myth lead people to spread, despite formal results [22] and practical see problems with capabilities that do not actually exist. systems [1, 9, 18, 21] demonstrating that they can do these supposedly impossible things. The prevalence of these myths is due to differing inter- pretations of the capability security model. To clear up We believe these severe misunderstandings are rooted the confusion, we examine three different models that in the fact that the term capability has come to be have been used to describe capabilities, and define a set portrayed in terms of several very different security of seven security properties that capture the distinctions models.
    [Show full text]
  • CS140 – Operating Systems
    CS140 – Operating Systems Instructors: Adam Belay, Ali Mashtizadeh, David Mazieres` CAs: Michael Chang, Peter Johnston, Yutian Liu, Rush Moody, Rasmus Rygaard, Jayesh Yerrapragada Stanford University 1 / 33 Administrivia • Class web page: http://cs140.scs.stanford.edu/ - All assignments, handouts, lecture notes on-line • Textbook: Operating System Concepts, 8th Edition, by Silberschatz, Galvin, and Gagne - 9th edition is way more expensive, I haven’t looked at it - Trying to ween class from textbook anyway—consider it optional • Goal is to make lecture slides the primary reference - Almost everything I talk about will be on slides - PDF slides contain links to further reading about topics - Please download slides from class web page 2 / 33 Administrivia 2 • Staff mailing list: [email protected] - Please mail staff list rather than individuals for help • Google group 15wi-cs140 is main discussion forum • Key dates: - Lectures: MW 4:15–5:30pm, Gates B01 - Section: Some Fridays, time/location TBD - Midterm: Monday, Feb 9, 4:15–5:30pm (in class) - Final: Thursday, March 19, 12:15pm–3:15pm • Exams open note, but not open book - Bring notes, slides, any printed materials except textbook - No electronic devices permitted 3 / 33 Lecture videos • Lectures will be televised for SCPD students - Can also watch if you miss a lecture, or to review - But resist temptation to miss a bunch of lectures and watch them all at once • SCPD students welcome to attend lecture in person - 4:15pm lecture time conveniently at end of work day - Many parking
    [Show full text]
  • Linux Internals
    LINUX INTERNALS Peter Chubb and Etienne Le Sueur [email protected] A LITTLE BIT OF HISTORY • Ken Thompson and Dennis Ritchie in 1967–70 • USG and BSD • John Lions 1976–95 • Andrew Tanenbaum 1987 • Linux Torvalds 1991 NICTA Copyright c 2011 From Imagination to Impact 2 The history of UNIX-like operating systems is a history of people being dissatisfied with what they have and wanting to do some- thing better. It started when Ken Thompson got bored with MUL- TICS and wanted to write a computer game (Space Travel). He found a disused PDP-7, and wrote an interactive operating sys- tem to run his game. The main contribution at this point was the simple file-system abstraction. (Ritchie 1984) Other people found it interesting enough to want to port it to other systems, which led to the first major rewrite — from assembly to C. In some ways UNIX was the first successfully portable OS. After Ritchie & Thompson (1974) was published, AT&T became aware of a growing market for UNIX. They wanted to discourage it: it was common for AT&T salesmen to say, ‘Here’s what you get: A whole lot of tapes, and an invoice for $10 000’. Fortunately educational licences were (almost) free, and universities around the world took up UNIX as the basis for teaching and research. The University of California at Berkeley was one of those univer- NICTA Copyright c 2011 From Imagination to Impact 2-1 sities. In 1977, Bill Joy (a postgrad) put together and released the first Berkeley Software Distribution — in this instance, the main additions were a pascal compiler and Bill Joy’s ex editor.
    [Show full text]
  • File Descriptors
    ���������������� �����������������everything is a file � main.c � a.out � /dev/sda1����������������� � /dev/tty2������������� � /proc/cpuinfo������������������������������� � ��������������������������������� ���������������������������������� ��file descriptor������������������������������������������� ������������������int ��� ������������� #include <sys/types.h> #include <sys/stat.h> #include <fcntl.h> int open(const char *path, int flags); ������������������flags��������������O_RDONLY� O_WRONLY�����O_RDWR �������O_CREAT�������������������������� #include <unistd.h> int close(int fd); ����������������������� � ������������������� #include <unistd.h> ssize_t read(int fd, void *buf, size_t n); ���������� fd����������������n������������buf #include <unistd.h> ssize_t write(int fd, const void *buf, size_t n); ���������fd��������������n������������buf ����������������������������������������������������� ���-1������������� � ����������������������� #include "csapp.h" ������ int main(int argc, char **argv) { ELF int fd = Open(argv[0], O_RDONLY, 0); char buf[5]; Read(fd, buf, 4); buf[4] = 0; printf("%s\n", buf+1); return 0; } ���� ����� ��������������� #include <unistd.h> int pipe(int fds[2]); ����������������������� ������������������������������ � fds[0]���������������� � fds[1]����������������� �� ���������������������������� #include "csapp.h" ������ int main(int argc, char **argv) { Hello int fds[2]; char buf[6]; Pipe(fds); Write(fds[1], "Hello", 5); Read(fds[0], buf, 5); buf[5] = 0; printf("%s\n", buf); return 0; } ���� ����� ���������������������������������
    [Show full text]