UNIX网络编程：进程间通信深入解析

5星 · 超过95%的资源需积分: 20 134 浏览量更新于2024-07-24 收藏 18.9MB PDF 举报

"UNIX网络编程 Vol.2-进程间通信-英文版-第二版，由W. Richard Stevens撰写，深入解析了UNIX系统中的进程间通信机制，包括消息传递、同步、共享内存以及远程过程调用。" 在《UNIX网络编程》第二版中，作者W. Richard Stevens，一个备受尊敬的UNIX专家，详细阐述了进程间通信（IPC）的各种方法和技术，这对于编写高性能的UNIX程序至关重要。IPC允许不同的进程之间共享数据和协调操作，是构建分布式和网络应用程序的基础。本书首先介绍了IPC的基本概念和目标，帮助读者理解IPC在解决多进程协同工作时的问题上所扮演的角色。然后，它逐步引导读者掌握System V IPC和新的POSIX标准，这两个标准提供了更便捷和高效的IPC解决方案。在消息传递方面，书中涵盖了管道（Pipe）和先进先出（FIFO）通信方式，以及POSIX和System V的信号队列。这些技术允许进程之间交换小块数据，实现数据的有序传输。同步机制是IPC的另一个关键组成部分，书中详细讲解了互斥锁（Mutexes）、条件变量（Condition Variables）、读写锁（Read-Write Locks）、文件与记录锁，以及信号量（Semaphores）。这些工具用于控制对共享资源的访问，确保数据的一致性和完整性。在共享内存部分，Stevens探讨了匿名共享内存和具名共享内存，这种技术允许多个进程直接访问同一块内存，从而提高效率。此外，还涉及了Solaris门和Sun RPC，这两种远程过程调用（RPC）技术，使得不同机器上的进程能够像在同一台机器上一样进行通信。为了帮助读者深化理解，书中每个主题都配有精心设计的练习题，并提供了一部分答案。通过实践，读者可以更好地掌握这些复杂的IPC技术。性能测量是本书的另一大亮点，Stevens介绍了一系列方法来评估不同IPC技术的性能，这有助于开发者选择最适合特定应用的通信机制。《UNIX网络编程 Vol.2》是一部深入且权威的IPC指南，对于网络研究和开发人员来说，它不仅提供了理论知识，还有丰富的实战经验，是提升技能不可或缺的参考资料。

xiv

UNIX

Network Programming Preface

able to run at the same time (on different

CPUs), or the multiple threads of a given pro

cess might be able to run at the same time. Therefore, distributing an application

among multiple processes or threads might reduce the amount of time required for an

application to perform a given task.

This book describes four different forms of IPC in detail:

message passing (pipes,

FIFOs,

and message queues),

2. synchronization (mutexes, condition variables, read

write locks, file and record

locks, and semaphores),

3. shared memory (anonymous and named), and

4. remote procedure calls

(Solaris doors and Sun RPC).

This book does not cover the writing of programs that communicate across a computer

network. This form of communication normally involves what is called the

sockets API

(application program interface) using the TCP/IP protocol suite; these topics are cov

ered in detail in Volume

of this series [Stevens 19981.

One could argue that single

host or nonnetworked IPC (the subject of this volume)

should not be used and instead all applications should be written as distributed appli

cations that run on various hosts across a network. Practically, however, single

host IPC

is often much faster and sometimes simpler than communicating across a network.

Techniques such as shared memory and synchronization are normally available only on

a single host, and may not be used across a network. Experience and

history have

shown a need for both nonnetworked IPC (this volume) and IPC across a network

(Volume

of this series).

This current volume builds on the foundation of Volume

and my other four books,

which are abbreviated throughout this text as follows:

UNPv1:

UNIX Network Programming, Volume

[Stevens 19981,

APUE:

Advanced Programming in the UNIX Environment

[Stevens 19921,

TCPv1:

TCPIIP Illustrated, Volume

[Stevens 19941,

TCPv2:

TCPIIP Illustrated, Volume

[Wright and Stevens 19951, and

TCPv3:

TCPIIP Illustrated, Volume

[Stevens 19961.

Although covering IPC in a text with

network programming

in the title might

seem odd, IPC is often used in networked applications. As stated in the Preface of the

1990 edition of

UNIX Network Programming,

requisite for understanding how to

develop software for a network is an understanding of interprocess communication

(IPC)."

Changes from the First Edition

This volume is a complete rewrite and expansion of Chapters 3 and 18 from the 1990

edition of

UNlX Network Programming.

Based on

word count, the material has

expanded by a factor of five. The following are the major changes with this new edi

tion:

UNIX

Network Programming

Preface

In addition to the three forms of

System

IPC

(message queues, semaphores,

and shared memory), the newer Posix functions that implement these three

types of IPC are also covered. (I say more about the Posix family of standards

Section 1.7.)

the coming years, I expect a movement to the Posix IPC func

tions, which have several advantages over their System

counterparts.

The Posix functions for synchronization are covered: mutex locks, condition

variables, and read

write locks. These can be used to synchronize either threads

or processes and are often used when accessing shared memory.

This volume assumes a Posix threads environment (called

Pthreads

), and

many of the examples are built using multiple threads instead of multiple pro

cesses.

The coverage of pipes, FIFOs, and record locking focuses on their Posix defini

tions.

addition to describing the IPC facilities and showing how to use them, I also

develop implementations of Posix message queues, read

write locks, and Posix

semaphores (all of which can be implemented as user libraries). These imple

mentations can tie together many different features (e-g., one implementation of

Posix semaphores uses mutexes, condition variables, and memory

mapped 1/01

and highlight conditions that must often be handled in our applications (such as

race conditions, error handling, memory leaks, and variable

length argument

lists). Understanding an implementation of a certain feature often leads to a

greater knowledge of how to use that feature.

The RPC coverage focuses on the Sun RPC package. I precede this with a

description of the new

Solaris doors API, which is similar to RPC but on a single

host. This provides an introduction to many of the features that we need to

worry about when calling procedures in another process, without having to

worry about any networking details.

Readers

This text can be used either as a tutorial on IPC, or as a reference for experienced pro

grammers. The book is divided into four main parts:

message passing,

synchronization,

shared memory, and

remote procedure calls

but many readers will probably be interested in speafic subsets. Most chapters can be

read independently of others, although Chapter

summarizes many features common

to all the Posix IPC functions, Chapter

summarizes many features common to all the

System

IPC functions, and Chapter 12 is an introduction to both Posix and System

shared memory. All readers should read Chapter 1, especially Section 1.6, which

describes some wrapper functions used throughout the text. The Posix IPC chapters are

xvi

UNIX

Network Programming Preface

independent of the System V IPC chapters, and the chapters on pipes,

FIFOs, and record

locking belong to neither camp. The two chapters on RPC are also independent of the

other IPC techniques.

To aid in the use as a reference,

thorough index

provided, along with sum

maries on the end papers of where to find detailed descriptions of all the functions and

structures. To help those reading topics in a random order, numerous references to

related topics are provided throughout the text.

Source Code and Errata Availability

The source code for all the examples that appear in this book is available from the

author's home page

(listed at the end of this Preface). The best way to learn the IPC

techniques described in this book is to take these programs, modify them, and enhance

them. Actually writing code of this form is the

only

way to reinforce the concepts and

techniques. Numerous exercises are also provided at the end of each chapter, and most

answers are provided in Appendix

A current errata for this book is also available from the author's home page.

Acknowledgments

Although the author's name is the only one to appear on the cover, the combined effort

of many people is required to produce a quality text book. First and foremost is the

author's family, who put up with the long and weird hours that go into writing a book.

Thank you once again, Sally, Bill, Ellen, and David.

My thanks to the technical reviewers who provided invaluable feedback

(135

printed pages) catching lots of errors, pointing out areas that needed more explanation,

and suggesting alternative presentations, wording, and coding: Gavin Bowe, Allen

Briggs, Dave Butenhof, Wan

Teh Chang, Chris Cleeland, Bob Friesenhahn, Andrew

Gierth, Scott Johnson, Marty Leisner, Larry McVoy, Craig Metz, Bob Nelson, Steve Rago,

Jim Reid, Swamy

Sitarama, Jon C. Snader, Ian Lance Taylor, Rich Teer, and Andy

Tucker.

The following people answered

email questions of mine, in some cases

many

ques

tions, all of which improved the accuracy and presentation of the text: David Bausum,

Dave Butenhof, Bill Gallmeister, Mukesh Kacker, Brian Kernighan, Larry

McVoy, Steve

Rago, Keith Skowran, Bart Smaalders, Andy Tucker, and John Wait.

A special thanks to Larry Rafsky at

GSquared, for lots of things. My thanks as

usual to the National Optical Astronomy Observatories

(NOAO), Sidney Wolff, Richard

Wolff, and Steve Crandi, for providing access to their networks and hosts. Jim Bound,

Matt Thomas, Mary Clouter, and Barb Glover of Digital Equipment Corp. provided the

Alpha system used for most of the examples in this text. A subset of the code in this

book was tested on other Unix systems: my thanks to

Michael Johnson of Red Hat Soft

ware for providing the latest releases of Red Hat Linux, and to Dave Marquardt and

Jessie Haug of IBM Austin for an

RS/6000 system and access to the latest releases of

AIX.

剩余563页未读，继续阅读

hrb_qiuyb

粉丝: 44
资源: 9

UNIX网络编程：进程间通信深入解析

（3/4）Unix Network Programming vol1 & vol2 - Unix网络编程第1卷 第2卷

Richard.Stevens.-.Unix.Network.Programming.Vol.1.(Addison-Wesley).7z.005

Prentice - Unix Network Programming Vol. 2.pdf

nexus-3.58.0-01-unix.tar.gz

nexus-3.61.0-02-unix.tar.gz 下载

nexus-3.35.0-02-unix 下载

如果执行命令#chmod 746 file.txt，那么该文件的权限是（ ）。 A.rwxr--rw-- B.rw-r--r-- C.--xr--rwx D.rwxr--r---

nexus-3.49.0-02-unix.tar.gz

最新资源

（3/4）Unix Network Programming vol1 & vol2 - Unix网络编程第1卷第2卷

如果执行命令#chmod 746 file.txt，那么该文件的权限是（）。 A.rwxr--rw-- B.rw-r--r-- C.--xr--rwx D.rwxr--r---