UNIX网络编程2：深入IPC与多线程技术详解

需积分: 20 106 浏览量更新于2024-07-23 收藏 18.9MB PDF 举报

"《UNIX网络编程2英文版》是传奇的UNIX专家Richard Stevens撰写的一本经典著作，该书在第二版中深入探讨了在非平凡UNIX程序性能优化中的核心要素——进程间通信（IPC）。作者从基础概念出发，逐步引导读者理解IPC的目的及其解决的问题，旨在帮助开发者最大限度地利用System V IPC标准和后来的POSIX标准，这些新标准极大地提升了便利性和性能。书中详尽介绍了各种形式的IPC技术，如消息传递、同步、共享内存以及远程过程调用（RPC），这些都是构建高效系统的关键组件。特别地，Stevens强调了在多线程环境下使用Pthreads的重要性，通过大量实例展示了如何在多个线程而非进程之间进行协作。他涵盖了诸如管道和FIFO、POSIX和System V信号量、POSIX和System V消息队列、POSIX和System V共享内存，还有Sun RPC等现代IPC手段。此外，书中还涉及了对IPC技术的性能测量，让读者能够评估不同策略的效果，这对于优化程序设计至关重要。《UNIX网络编程2》不仅是对UNIX系统内核与网络通信的深度解析，也是提升软件开发人员在分布式环境下的编程能力的实用指南。无论是初学者还是经验丰富的开发者，都能从中收获宝贵的知识和技巧，以实现更高效、稳定的网络应用程序。"

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页未读，继续阅读

cschengvdn

粉丝: 34
资源: 18

UNIX网络编程2：深入IPC与多线程技术详解

Unix网络编程英文版PDF

unix网络编程（英文版）

UNIX网络编程（第2版）

Unix网络编程 中英文版

Unix网络编程(英文版)

UNIX网络编程英文版

UNIX网络编程 英文版

unix网络编程中英文版高清PDF+源代码

unix网络编程 英文版 3

UNIX网络编程 UNIX网络编程

最新资源

Unix网络编程中英文版

UNIX网络编程英文版

unix网络编程英文版 3