Lab2.html 52 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172
  1. <!DOCTYPE html>
  2. <html lang="en-US">
  3. <head>
  4. <meta charset="utf-8">
  5. <meta name="viewport" content="width=device-width,initial-scale=1">
  6. <title>进程创建与进程间通信 | 操作系统实验</title>
  7. <meta name="generator" content="VuePress 1.9.10">
  8. <meta name="description" content="Welcome!">
  9. <link rel="preload" href="/OS_lab_tutorial/assets/css/0.styles.dbcc0abd.css" as="style"><link rel="preload" href="/OS_lab_tutorial/assets/js/app.de832b6b.js" as="script"><link rel="preload" href="/OS_lab_tutorial/assets/js/2.6cca19a7.js" as="script"><link rel="preload" href="/OS_lab_tutorial/assets/js/1.2e5d3cee.js" as="script"><link rel="preload" href="/OS_lab_tutorial/assets/js/26.7dca1b95.js" as="script"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/10.e3ae3b6e.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/11.c389195a.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/12.15e02b09.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/13.e100960d.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/14.3675c8e8.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/15.5542c093.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/16.01c35b5f.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/17.bd8d538c.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/18.6d3b94c1.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/19.eb35cfee.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/20.c11ec329.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/21.160e1109.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/22.8c6c68bf.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/23.6c245a02.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/24.c2cc382b.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/25.3a441277.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/27.9fdfa008.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/28.ea152bf8.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/29.310b119e.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/3.5322f14a.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/30.1be87618.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/31.e60e769a.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/32.ed12ff5e.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/33.d0e6ffd8.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/34.fb25dd7d.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/35.38b1a166.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/36.f2dcdc62.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/37.85edb076.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/38.a07efacb.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/39.2e2bced7.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/4.ba0ffc9e.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/40.7564ba2d.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/41.7bc98649.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/42.ee9b7b13.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/43.dbdee45b.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/44.f24405f8.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/45.bebd92ee.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/46.5d70de3f.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/47.0df811bd.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/48.3f21f3a0.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/49.4ceb6d85.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/5.1674539b.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/50.9d21087d.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/51.760bed26.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/52.78b43a02.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/53.fd428cc4.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/54.4937721a.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/55.b040b54f.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/56.f538318b.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/57.47c5385e.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/58.c8103992.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/59.7a4c397a.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/6.44f67c6a.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/60.1f64a100.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/61.8ebdd979.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/62.6cab9dfb.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/63.380a795e.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/64.57bfd1e1.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/65.54ffadf5.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/66.dccb9c04.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/7.21830bc0.js"><link rel="prefetch" href="/OS_lab_tutorial/assets/js/vendors~docsearch.cf079a49.js">
  10. <link rel="stylesheet" href="/OS_lab_tutorial/assets/css/0.styles.dbcc0abd.css">
  11. </head>
  12. <body>
  13. <div id="app" data-server-rendered="true"><div class="theme-container"><header class="navbar"><div class="sidebar-button"><svg xmlns="http://www.w3.org/2000/svg" aria-hidden="true" role="img" viewBox="0 0 448 512" class="icon"><path fill="currentColor" d="M436 124H12c-6.627 0-12-5.373-12-12V80c0-6.627 5.373-12 12-12h424c6.627 0 12 5.373 12 12v32c0 6.627-5.373 12-12 12zm0 160H12c-6.627 0-12-5.373-12-12v-32c0-6.627 5.373-12 12-12h424c6.627 0 12 5.373 12 12v32c0 6.627-5.373 12-12 12zm0 160H12c-6.627 0-12-5.373-12-12v-32c0-6.627 5.373-12 12-12h424c6.627 0 12 5.373 12 12v32c0 6.627-5.373 12-12 12z"></path></svg></div> <a href="/OS_lab_tutorial/" class="home-link router-link-active"><!----> <span class="site-name">操作系统实验</span></a> <div class="links"><div class="search-box"><input aria-label="Search" autocomplete="off" spellcheck="false" value=""> <!----></div> <nav class="nav-links can-hide"><div class="nav-item"><a href="/OS_lab_tutorial/" class="nav-link">
  14. 首页
  15. </a></div><div class="nav-item"><div class="dropdown-wrapper"><button type="button" aria-label="Linux" class="dropdown-title"><span class="title">Linux</span> <span class="arrow down"></span></button> <button type="button" aria-label="Linux" class="mobile-dropdown-title"><span class="title">Linux</span> <span class="arrow right"></span></button> <ul class="nav-dropdown" style="display:none;"><li class="dropdown-item"><h4>
  16. 实验教程
  17. </h4> <ul class="dropdown-subitem-wrapper"><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Lab/Lab1.html" class="nav-link">
  18. 实验1-熟悉类Linux系统
  19. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html" aria-current="page" class="nav-link router-link-exact-active router-link-active">
  20. 实验2-进程创建与进程间通信
  21. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Lab/Lab3/" class="nav-link">
  22. 实验3-进程调度算法
  23. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Lab/Lab4/" class="nav-link">
  24. 实验4-存储管理算法
  25. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Lab/Lab5.html" class="nav-link">
  26. 实验5-文件管理系统
  27. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Lab/Lab6.html" class="nav-link">
  28. 实验6-网络编程(暂定)
  29. </a></li></ul></li><li class="dropdown-item"><h4>
  30. 课程练习
  31. </h4> <ul class="dropdown-subitem-wrapper"><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Assignment/Lab1.html" class="nav-link">
  32. 实验1-熟悉类Linux系统
  33. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Assignment/Lab2.html" class="nav-link">
  34. 实验2-进程创建与进程间通信
  35. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Assignment/Lab3.html" class="nav-link">
  36. 实验3-进程调度算法
  37. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Assignment/Lab4.html" class="nav-link">
  38. 实验4-存储管理算法
  39. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Assignment/Lab5.html" class="nav-link">
  40. 实验5-文件管理系统
  41. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Assignment/Lab6.html" class="nav-link">
  42. 实验6-网络编程(暂定)
  43. </a></li></ul></li><li class="dropdown-item"><h4>
  44. 附录
  45. </h4> <ul class="dropdown-subitem-wrapper"><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Appendix/Lab1.html" class="nav-link">
  46. 实验1-熟悉类Linux系统
  47. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Appendix/Lab2.html" class="nav-link">
  48. 实验2-进程创建与进程间通信
  49. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Appendix/Lab3.html" class="nav-link">
  50. 实验3-进程调度算法
  51. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Appendix/Lab4.html" class="nav-link">
  52. 实验4-存储管理算法
  53. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Appendix/Lab5.html" class="nav-link">
  54. 实验5-文件管理系统
  55. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Appendix/Lab6.html" class="nav-link">
  56. 实验6-网络编程(暂定)
  57. </a></li></ul></li></ul></div></div><div class="nav-item"><div class="dropdown-wrapper"><button type="button" aria-label="DragonOS" class="dropdown-title"><span class="title">DragonOS</span> <span class="arrow down"></span></button> <button type="button" aria-label="DragonOS" class="mobile-dropdown-title"><span class="title">DragonOS</span> <span class="arrow right"></span></button> <ul class="nav-dropdown" style="display:none;"><li class="dropdown-item"><h4>
  58. 实验教程
  59. </h4> <ul class="dropdown-subitem-wrapper"><li class="dropdown-subitem"><a href="/OS_lab_tutorial/DragonOS/Lab/Lab1.html" class="nav-link">
  60. 实验-文件系统
  61. </a></li></ul></li><li class="dropdown-item"><h4>
  62. 课程练习
  63. </h4> <ul class="dropdown-subitem-wrapper"><li class="dropdown-subitem"><a href="/OS_lab_tutorial/DragonOS/Assignment/Lab1.html" class="nav-link">
  64. 实验-文件系统
  65. </a></li></ul></li><li class="dropdown-item"><h4>
  66. 附录
  67. </h4> <ul class="dropdown-subitem-wrapper"><li class="dropdown-subitem"><a href="/OS_lab_tutorial/DragonOS/Appendix/Lab1.html" class="nav-link">
  68. 实验-文件系统
  69. </a></li></ul></li></ul></div></div> <!----></nav></div></header> <div class="sidebar-mask"></div> <aside class="sidebar"><nav class="nav-links"><div class="nav-item"><a href="/OS_lab_tutorial/" class="nav-link">
  70. 首页
  71. </a></div><div class="nav-item"><div class="dropdown-wrapper"><button type="button" aria-label="Linux" class="dropdown-title"><span class="title">Linux</span> <span class="arrow down"></span></button> <button type="button" aria-label="Linux" class="mobile-dropdown-title"><span class="title">Linux</span> <span class="arrow right"></span></button> <ul class="nav-dropdown" style="display:none;"><li class="dropdown-item"><h4>
  72. 实验教程
  73. </h4> <ul class="dropdown-subitem-wrapper"><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Lab/Lab1.html" class="nav-link">
  74. 实验1-熟悉类Linux系统
  75. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html" aria-current="page" class="nav-link router-link-exact-active router-link-active">
  76. 实验2-进程创建与进程间通信
  77. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Lab/Lab3/" class="nav-link">
  78. 实验3-进程调度算法
  79. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Lab/Lab4/" class="nav-link">
  80. 实验4-存储管理算法
  81. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Lab/Lab5.html" class="nav-link">
  82. 实验5-文件管理系统
  83. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Lab/Lab6.html" class="nav-link">
  84. 实验6-网络编程(暂定)
  85. </a></li></ul></li><li class="dropdown-item"><h4>
  86. 课程练习
  87. </h4> <ul class="dropdown-subitem-wrapper"><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Assignment/Lab1.html" class="nav-link">
  88. 实验1-熟悉类Linux系统
  89. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Assignment/Lab2.html" class="nav-link">
  90. 实验2-进程创建与进程间通信
  91. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Assignment/Lab3.html" class="nav-link">
  92. 实验3-进程调度算法
  93. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Assignment/Lab4.html" class="nav-link">
  94. 实验4-存储管理算法
  95. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Assignment/Lab5.html" class="nav-link">
  96. 实验5-文件管理系统
  97. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Assignment/Lab6.html" class="nav-link">
  98. 实验6-网络编程(暂定)
  99. </a></li></ul></li><li class="dropdown-item"><h4>
  100. 附录
  101. </h4> <ul class="dropdown-subitem-wrapper"><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Appendix/Lab1.html" class="nav-link">
  102. 实验1-熟悉类Linux系统
  103. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Appendix/Lab2.html" class="nav-link">
  104. 实验2-进程创建与进程间通信
  105. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Appendix/Lab3.html" class="nav-link">
  106. 实验3-进程调度算法
  107. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Appendix/Lab4.html" class="nav-link">
  108. 实验4-存储管理算法
  109. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Appendix/Lab5.html" class="nav-link">
  110. 实验5-文件管理系统
  111. </a></li><li class="dropdown-subitem"><a href="/OS_lab_tutorial/Linux/Appendix/Lab6.html" class="nav-link">
  112. 实验6-网络编程(暂定)
  113. </a></li></ul></li></ul></div></div><div class="nav-item"><div class="dropdown-wrapper"><button type="button" aria-label="DragonOS" class="dropdown-title"><span class="title">DragonOS</span> <span class="arrow down"></span></button> <button type="button" aria-label="DragonOS" class="mobile-dropdown-title"><span class="title">DragonOS</span> <span class="arrow right"></span></button> <ul class="nav-dropdown" style="display:none;"><li class="dropdown-item"><h4>
  114. 实验教程
  115. </h4> <ul class="dropdown-subitem-wrapper"><li class="dropdown-subitem"><a href="/OS_lab_tutorial/DragonOS/Lab/Lab1.html" class="nav-link">
  116. 实验-文件系统
  117. </a></li></ul></li><li class="dropdown-item"><h4>
  118. 课程练习
  119. </h4> <ul class="dropdown-subitem-wrapper"><li class="dropdown-subitem"><a href="/OS_lab_tutorial/DragonOS/Assignment/Lab1.html" class="nav-link">
  120. 实验-文件系统
  121. </a></li></ul></li><li class="dropdown-item"><h4>
  122. 附录
  123. </h4> <ul class="dropdown-subitem-wrapper"><li class="dropdown-subitem"><a href="/OS_lab_tutorial/DragonOS/Appendix/Lab1.html" class="nav-link">
  124. 实验-文件系统
  125. </a></li></ul></li></ul></div></div> <!----></nav> <ul class="sidebar-links"><li><section class="sidebar-group depth-0"><p class="sidebar-heading open"><span>进程创建与进程间通信</span> <!----></p> <ul class="sidebar-links sidebar-group-items"><li><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#本章导读" class="sidebar-link">本章导读</a><ul class="sidebar-sub-headers"></ul></li><li><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#进程创建" class="sidebar-link">进程创建</a><ul class="sidebar-sub-headers"><li class="sidebar-sub-header"><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#什么是进程" class="sidebar-link">什么是进程?</a></li><li class="sidebar-sub-header"><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#创建进程" class="sidebar-link">创建进程</a></li><li class="sidebar-sub-header"><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#系统调用fork" class="sidebar-link">系统调用fork()</a></li></ul></li><li><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#与进程相关的系统调用" class="sidebar-link">与进程相关的系统调用</a><ul class="sidebar-sub-headers"><li class="sidebar-sub-header"><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#execv系统调用" class="sidebar-link">execv系统调用</a></li><li class="sidebar-sub-header"><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#wait系统调用" class="sidebar-link">wait系统调用</a></li><li class="sidebar-sub-header"><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#exit系统调用" class="sidebar-link">exit系统调用</a></li><li class="sidebar-sub-header"><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#lockf系统调用" class="sidebar-link">lockf系统调用</a></li></ul></li><li><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#进程间通信" class="sidebar-link">进程间通信</a><ul class="sidebar-sub-headers"><li class="sidebar-sub-header"><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#进程间通信的概念" class="sidebar-link">进程间通信的概念</a></li><li class="sidebar-sub-header"><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#无名管道-pipe" class="sidebar-link">无名管道(pipe)</a></li><li class="sidebar-sub-header"><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#命名管道-fifo" class="sidebar-link">命名管道(FIFO)</a></li><li class="sidebar-sub-header"><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#用于管道通信的函数" class="sidebar-link">用于管道通信的函数</a></li><li class="sidebar-sub-header"><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#信号" class="sidebar-link">信号</a></li><li class="sidebar-sub-header"><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#信号量" class="sidebar-link">信号量</a></li><li class="sidebar-sub-header"><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#消息队列" class="sidebar-link">消息队列</a></li><li class="sidebar-sub-header"><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#共享内存" class="sidebar-link">共享内存</a></li><li class="sidebar-sub-header"><a href="/OS_lab_tutorial/Linux/Lab/Lab2.html#套接字" class="sidebar-link">套接字</a></li></ul></li></ul></section></li></ul> </aside> <main class="page"> <div class="theme-default-content content__default"><h1 id="进程创建与进程间通信"><a href="#进程创建与进程间通信" class="header-anchor">#</a> 进程创建与进程间通信</h1> <h2 id="本章导读"><a href="#本章导读" class="header-anchor">#</a> 本章导读</h2> <p>本章意在介绍进程创建和进程间通信相关知识,</p> <h2 id="进程创建"><a href="#进程创建" class="header-anchor">#</a> 进程创建</h2> <h3 id="什么是进程"><a href="#什么是进程" class="header-anchor">#</a> 什么是进程?</h3> <p>通过操作系统这门课我们知道,在多道程序环境下,允许多个程序并发执行,此时它们将失去封闭性,并具有间断性及不可再现性的特征。为此引入了进程的概念,以便更好地描述和控制程序的并发执行,实现操作系统的并发性和共享性(最基本的两个特性)。</p> <p><strong>进程</strong>表示程序的一次执行过程,它是应用程序的运行实例,是一个动态的过程。或者可以更简单地描述为:进程是操作系统当前运行的程序。当一个进程开始运行时,就是启动了这个过程。进程包括动态执行的程序和数据两部分。</p> <p>为了对系统中的所有进程实施有效的管理,引入了<strong>进程控制</strong>的概念,它具有创建新进程、撤销已有进程、实现进程状态转换等功能。</p> <h3 id="创建进程"><a href="#创建进程" class="header-anchor">#</a> 创建进程</h3> <p>在Linux系统中,除了系统启动之后的第一个进程由系统来创建,其余的进程都必须由已存在的进程来创建,新创建的进程叫做<strong>子进程</strong>,而创建子进程的进程叫做<strong>父进程</strong>。那个在系统启动及完成初始化之后,Linux自动创建的进程叫做<strong>根进程</strong>。<strong>根进程</strong>是Linux中所有进程的祖宗,其余进程都是根进程的子孙。另外,具有同一个父进程的进程叫做<strong>兄弟进程</strong>。</p> <p>进程创建的过程示意图如下所示:</p> <img src="/OS_lab_tutorial/assets/img/process.6dac9f0a.png" alt="图片1" title="进程的创建" style="zoom:67%;"> <h3 id="系统调用fork"><a href="#系统调用fork" class="header-anchor">#</a> 系统调用fork()</h3> <p>在Linux中,父进程以分裂的方式来创建子进程,为了在一个进程中分裂出子进程,Linux提供了一个系统调用<code>fork()</code>。这里所说的分裂,实际上是一种复制。因为在系统中表示一个进程的实体是<strong>进程控制块(PCB)</strong>,创建新进程的主要工作就是要创建一个新控制块,而创建一个新控制块最简单的方法就是复制。</p> <p>当然,这里的复制并不是完全复制,因为父进程控制块中某些项的内容必须按照子进程的特性来修改,例如进程的标识、状态等。另外,子进程控制块还必须要有表示自己父进程的域和私有空间,例如数据空间、用户堆栈等。</p> <p>进程调用<code>fork()</code>,当控制转移到内核中的fork代码后,内核会做:</p> <ul><li>分配新的内存块和内核数据结构给子进程。</li> <li>将父进程部分数据结构内容拷贝至子进程。</li> <li>添加子进程到系统进程列表当中。</li> <li>fork返回,开始调度器调度。</li></ul> <p>在父进程中调用<code>fork()</code>之后会产生两种结果:一种为分裂子进程失败,另一种就是分裂子进程成功。<code>fork()</code>调用的一个奇妙之处在于它仅仅被调用一次,却能够返回两次,可能有三种不同的返回值:</p> <ol><li>在父进程中,返回新创建子进程的进程ID;</li> <li>在子进程中,返回0;</li> <li>如果出现错误,返回一个负值。</li></ol> <p>在<code>fork()</code>执行完毕后,如果创建新进程成功,则出现两个进程,一个是子进程,一个是父进程。我们可以通过<code>fork()</code>返回的值来判断当前进程是子进程还是父进程。</p> <blockquote><p>为什么子进程返回0,父进程返回子进程的PID?</p> <blockquote><p>我们可以这样理解,进程形成了链表,<code>fork()</code>返回的是进程的fpid,父进程的fpid指向子进程的进程id, 因为子进程没有子进程,所以其fpid为 0。</p></blockquote></blockquote> <blockquote><p>为什么<code>fork()</code>会返回两次?</p> <blockquote><p>在fork函数内部执行return语句之前,子进程就已经创建完毕了,那么之后的return语句不仅父进程需要执行,子进程也同样需要执行,这就是fork函数有两个返回值的原因。</p></blockquote></blockquote> <p><strong>fork常规用法</strong></p> <ul><li>一个进程希望复制自己,使子进程同时执行不同的代码段。例如父进程等待客户端请求,生成子进程来处理请求。</li> <li>一个进程要执行一个不同的程序。例如子进程从fork返回后,调用exec函数。</li></ul> <p><strong>fork调用失败的原因</strong></p> <p>fork函数创建子进程也可能会失败,有以下两种情况:</p> <ol><li>系统中有太多的进程,内存空间不足,子进程创建失败。</li> <li>实际用户的进程数超过了限制,子进程创建失败。</li></ol> <h2 id="与进程相关的系统调用"><a href="#与进程相关的系统调用" class="header-anchor">#</a> 与进程相关的系统调用</h2> <h3 id="execv系统调用"><a href="#execv系统调用" class="header-anchor">#</a> execv系统调用</h3> <p>为了在程序运行中能够加载并运行一个可执行文件,Linux提供了系统调用 execv()</p> <p>将一个可执行的二进制文件覆盖在新进程的用户级上下文的存储空间上,以更改新进程的用户级上下文。调用进程被覆盖,从新程序的入口开始执行,这样就产生了一个新进程,进程标识符id不变。</p> <p><strong>函数原型</strong></p> <blockquote><p>参数 path 为可执行文件路径,argv[] 为命令行参数</p></blockquote> <div class="language-c extra-class"><pre class="language-c"><code><span class="token keyword">int</span> <span class="token function">execv</span><span class="token punctuation">(</span><span class="token keyword">const</span> <span class="token keyword">char</span><span class="token operator">*</span> path, <span class="token keyword">char</span><span class="token operator">*</span> <span class="token keyword">const</span> argv<span class="token punctuation">[</span><span class="token punctuation">]</span><span class="token punctuation">)</span><span class="token punctuation">;</span>
  126. </code></pre></div><p><strong>返回值</strong></p> <p>如果应用程序正常执行完毕,那么 execv 是永远不会返回的;当 execv 在调用进程中返回时,那么这个应用程序应该出错了,此时它的返回值应该是 -1,失败原因存于 errno 中</p> <p><strong>范例</strong></p> <div class="language-c extra-class"><pre class="language-c"><code><span class="token comment">// 执行/bin/ls -al /etc/passwd </span>
  127. <span class="token macro property"><span class="token directive-hash">#</span><span class="token directive keyword">include</span><span class="token string">&lt;unistd.h&gt;</span></span>
  128. <span class="token function">main</span><span class="token punctuation">(</span><span class="token punctuation">)</span>
  129. <span class="token punctuation">{</span>
  130. <span class="token keyword">char</span> <span class="token operator">*</span> argv<span class="token punctuation">[</span> <span class="token punctuation">]</span><span class="token operator">=</span><span class="token punctuation">{</span>“ls”,”<span class="token operator">-</span>al”,”<span class="token operator">/</span>etc<span class="token operator">/</span>passwd”,<span class="token punctuation">(</span><span class="token keyword">char</span><span class="token operator">*</span><span class="token punctuation">)</span><span class="token punctuation">}</span><span class="token punctuation">;</span>
  131. <span class="token function">execv</span><span class="token punctuation">(</span>“<span class="token operator">/</span>bin<span class="token operator">/</span>ls”,argv<span class="token punctuation">)</span><span class="token punctuation">;</span>
  132. <span class="token punctuation">}</span>
  133. </code></pre></div><blockquote><p>实际上存在一个 exec函数族,execv() 只是其中一个,他们的区别主要是</p> <ol><li>待执行的程序文件是由文件名(filename)还是由路径名(pathname)指定;</li> <li>新程序的参数是一一列出还是由一个指针数组来引用;</li> <li>把调用进程的环境传递给新程序还是给新程序指定新的环境</li></ol> <p>其作用都是相同的</p></blockquote> <h3 id="wait系统调用"><a href="#wait系统调用" class="header-anchor">#</a> wait系统调用</h3> <p>为使父进程在子进程结束之后释放子进程所占用的系统资源,父进程应该调用系统调用<code>wait()</code>。父进程与子进程同步,父进程调用后,进入睡眠状态,直到子进程结束或者父进程被其他进程终止。</p> <p><strong>系统调用格式:</strong></p> <div class="language-c extra-class"><pre class="language-c"><code><span class="token keyword">void</span> <span class="token function">exit</span><span class="token punctuation">(</span><span class="token keyword">int</span> <span class="token operator">*</span>status<span class="token punctuation">)</span>
  134. </code></pre></div><p>内核对wait( )作以下处理:</p> <ol><li>首先查找调用进程是否有子进程,若无,则返回出错码;</li> <li>若找到僵死进程,则将子进程的执行时间加到父进程的执行时间上,并释放子进程的进程表项;</li> <li>若未找到僵死进程,则调用进程便在可被中断的优先级上睡眠,等待其子进程发来软中断信号时被唤醒。</li></ol> <blockquote><p>僵死进程:一个进程使用fork创建子进程,如果子进程退出,而父进程并没有调用wait或waitpid获取子进程的状态信息,那么子进程的进程描述符仍然保存在系统中,也就是进程为中止状态。</p></blockquote> <h3 id="exit系统调用"><a href="#exit系统调用" class="header-anchor">#</a> exit系统调用</h3> <p>如果一个进程调用exit(),系统会立即停止所以操作,清除进程相关的各种数据结构,包括进程PCB,并且终止当前进程的运行。</p> <p><strong>系统调用格式:</strong></p> <div class="language-c extra-class"><pre class="language-c"><code><span class="token keyword">void</span> <span class="token function">exit</span><span class="token punctuation">(</span><span class="token keyword">int</span> status<span class="token punctuation">)</span>
  135. </code></pre></div><p>其中,status 是返回给父进程的一个整数,0 表示正常退出,其他表示非正常退出,一般使用 -1 或者 1。</p> <p><strong>进程终止的特殊情况</strong></p> <ol><li>子进程终止时,父进程并没有在执行 wait() 调用。</li></ol> <p>这时进程处于上文所提到僵死状态,处于这种状态的进程不使用任何内核资源,但是要占用内核中的进程处理表那的一项。当其父进程执行 wait() 等待子进程时,它会进入睡眠状态,然后把这种处于过渡状态的进程从系统内删除,父进程仍将能得到该子进程的结束状态。</p> <ol start="2"><li>当子进程尚未终止时,父进程却终止了。</li></ol> <p>对于⽗进程已经终⽌的所有子进程,他们的⽗进程都改变为 init 进程。我们称这些子进程由 init 领养。⼀个init的⼦进程(包括领养进程)终⽌时,init会调⽤⼀个 wait() 函数取得其终⽌状态。</p> <h3 id="lockf系统调用"><a href="#lockf系统调用" class="header-anchor">#</a> lockf系统调用</h3> <p>lockf()函数对指定区域的资源进行加锁或解锁,以实现进程的同步或互斥。</p> <p><strong>系统调用格式:</strong></p> <div class="language-c extra-class"><pre class="language-c"><code><span class="token macro property"><span class="token directive-hash">#</span><span class="token directive keyword">include</span> <span class="token string">&lt;unistd.h&gt;</span></span>
  136. <span class="token keyword">int</span> <span class="token function">lockf</span><span class="token punctuation">(</span><span class="token keyword">int</span> fd<span class="token punctuation">,</span> <span class="token keyword">int</span> mod<span class="token punctuation">,</span> <span class="token keyword">int</span> size<span class="token punctuation">)</span>
  137. </code></pre></div><blockquote><p><strong>fd</strong> 是打开文件的文件描述符</p> <p><strong>mod</strong> 是指定要采取的操作的控制值。1是进行锁定,0是解锁</p> <p><strong>size</strong> 是要锁定或解锁的连续字节数</p></blockquote> <p>两个常用命令:</p> <ol><li>当 size = 0 时是个特殊情况,它代表锁定区域从该函数到程序结尾。lockf(1,1,0)意思是该进程的编号为1,并对进程的资源进行锁定,锁定区域从该函数到程序结尾。</li> <li>lockf(1,0,0)是对编号为 1 的进程进行解锁,释放资源。</li></ol> <h2 id="进程间通信"><a href="#进程间通信" class="header-anchor">#</a> 进程间通信</h2> <h3 id="进程间通信的概念"><a href="#进程间通信的概念" class="header-anchor">#</a> 进程间通信的概念</h3> <p>进程用户空间是相互独立的,一般是不能相互访问的。但很多情况下进程之间需要互相通信,来完成系统的某项功能。进程通过与内核及其它进程之间的互相通信来协调它们的行为。</p> <p>Linux环境下的进程间通信(Inter-Process Communication,简称IPC)有多种工具可以使用,如:无名管道pipe、命名管道FIFO、消息队列、共享内存、信号量、信号、文件锁、socket等。这些IPC工具以系统调用或库函数API的形式提供给用户使用,用户使用这些API可以在不同的进程之间传输数据、同步进程、或者发送信号。</p> <p>每一种IPC通信工具,都有自己的优缺点、使用场合和局限,我们只有全面了解和掌握各个IPC工具的使用,知晓其优缺点,才能根据需要,选择合适的通信机制。</p> <h3 id="无名管道-pipe"><a href="#无名管道-pipe" class="header-anchor">#</a> 无名管道(pipe)</h3> <p>无名管道又称匿名管道,是一种半双工的通信方式,数据只能单向流动,而且只能在具有亲缘关系的进程间使用,进程的亲缘关系一般指的是父子关系。无名管道一般用于两个不同进程之间的通信。当一个进程创建了一个管道,并调用fork创建自己的一个子进程后,父进程关闭读管道端,子进程关闭写管道端,这样提供了两个进程之间数据流动的一种方式。</p> <p>这是一种最基本的IPC机制,由<strong>pipe函数</strong>创建:</p> <div class="language-c extra-class"><pre class="language-c"><code><span class="token macro property"><span class="token directive-hash">#</span><span class="token directive keyword">include</span> <span class="token string">&lt;unistd.h&gt;</span></span>
  138. <span class="token keyword">int</span> <span class="token function">pipe</span><span class="token punctuation">(</span><span class="token keyword">int</span> fd<span class="token punctuation">[</span><span class="token number">2</span><span class="token punctuation">]</span><span class="token punctuation">)</span><span class="token punctuation">;</span>
  139. </code></pre></div><p>pipe 函数的参数是一个包含两个 int 类型整数的数组指针。该函数成功时返回 0,并将一对打开的文件描述符值填入其参数指向的数组。如果失败,则返回 -1 并设置 errno。</p> <p>通过pipe函数创建的这两个文件描述符fd[0]和fd[1]分别构成管道的两端,往fd[1]写入的数据可以从fd[0]读出,并且fd[1]一端只能进行写操作,fd[0]一端只能进行读操作,不能反过来使用。要实现双向数据传输,可以使用两个管道。</p> <h3 id="命名管道-fifo"><a href="#命名管道-fifo" class="header-anchor">#</a> 命名管道(FIFO)</h3> <p>命名管道也是一种半双工的通信方式,但不用同于无名管道之处在于它提供一个路径名与之关联,以命名管道的文件形式存储文件系统中。命名管道是一个设备文件,因此即使进程与创建命名管道的进程不存在亲缘关系,只要可以访问该路径,就能够通过命名管道相互通信。</p> <p>Linux中通过系统调用<code>mknod()</code>或<code>mkfifo()</code>来创建一个命名管道。最简单的方式是通过直接使用shell:</p> <div class="language-shell extra-class"><pre class="language-shell"><code><span class="token comment"># 在当前目录下创建了一个名为myfifo的命名管道</span>
  140. <span class="token comment"># 两者等价</span>
  141. <span class="token function">mkfifo</span> myfifo
  142. <span class="token function">mknod</span> myfifo p
  143. </code></pre></div><p>返回值:均是成功返回0,失败返回-1。</p> <h3 id="用于管道通信的函数"><a href="#用于管道通信的函数" class="header-anchor">#</a> 用于管道通信的函数</h3> <h4 id="read"><a href="#read" class="header-anchor">#</a> <code>read()</code></h4> <p>从指定文件中读数据,并将它们送至所指示的缓冲区中。</p> <p><strong>系统调用格式:</strong></p> <div class="language-c extra-class"><pre class="language-c"><code><span class="token macro property"><span class="token directive-hash">#</span><span class="token directive keyword">include</span> <span class="token string">&lt;unistd.h&gt;</span> </span>
  144. <span class="token class-name">ssize_t</span> <span class="token function">read</span><span class="token punctuation">(</span><span class="token keyword">int</span> fd<span class="token punctuation">,</span> <span class="token keyword">void</span> <span class="token operator">*</span>buf<span class="token punctuation">,</span> <span class="token class-name">size_t</span> count<span class="token punctuation">)</span><span class="token punctuation">;</span>
  145. </code></pre></div><blockquote><p><strong>fd</strong> 是打开文件的文件描述符</p> <p><strong>buf</strong> 是指定缓冲区的指针</p> <p><strong>count</strong> 是要读取的字节数</p></blockquote> <p>返回值:成功则返回读取的字节数,出错则返回 -1 并设置 errno,如果在调 read 之前已到达文件末尾,则这次read返回 0。</p> <h4 id="write"><a href="#write" class="header-anchor">#</a> <code>write()</code></h4> <p>从指定文件中读数据,并将它们送至所指示的缓冲区中。</p> <p><strong>系统调用格式:</strong></p> <div class="language-c extra-class"><pre class="language-c"><code><span class="token macro property"><span class="token directive-hash">#</span><span class="token directive keyword">include</span> <span class="token string">&lt;unistd.h&gt;</span> </span>
  146. <span class="token class-name">ssize_t</span> <span class="token function">write</span><span class="token punctuation">(</span><span class="token keyword">int</span> fd<span class="token punctuation">,</span> <span class="token keyword">const</span> <span class="token keyword">void</span> <span class="token operator">*</span>buf<span class="token punctuation">,</span> <span class="token class-name">size_t</span> count<span class="token punctuation">)</span><span class="token punctuation">;</span>
  147. </code></pre></div><blockquote><p><strong>fd</strong> 是打开文件的文件描述符</p> <p><strong>buf</strong> 是指定缓冲区的指针</p> <p><strong>count</strong> 是要写入的字节数</p></blockquote> <p>返回值:成功返回写入的字节数,出错返回-1并设置errno写常规文件时,write的返回值通常等于请求写的字节数count。</p> <blockquote><p>管道作为临界资源,使用过程中父子进程之间除了需要读写同步以外,在对管道进行读写操作时还需要互斥进入,可以使用对文件上锁和开锁的系统调用lockf()。如果文件被加锁,将会等待,直到锁打开为止。</p></blockquote> <h3 id="信号"><a href="#信号" class="header-anchor">#</a> 信号</h3> <p>信号是比较复杂的通信方式,类似于Windows下的消息,用于通知接受进程有某种事件发生。除了用于进程间通信外,进程还可以发送信号给进程本身。Linux除了支持Unix早期信号语义函数<code>signal</code>外,还支持语义符合Posix.1标准的信号函数<code>sigaction</code>。</p> <p>每个信号都对应一个正整数常量(signal number,即信号编号),代表同一用户的诸进程之间传送事先约定的信息的类型,用于通知某进程发生了某异常事件。每个进程在运行时,都要通过信号机制来检查是否有信号到达。若有,便中断正在执行的程序,转向与该信号相对应的处理程序,以完成对该事件的处理;处理结束后再返回到原来的断点继续执行。实质上,信号机制是对中断机制的一种模拟,故在早期的UNIX版本中又把它称为软中断。</p> <p>信号的处理方式有3种:</p> <ol><li>忽略(放置不理)</li> <li>默认处理方式(会终止一个进程)</li> <li>响应信号处理(信号发生时执行预先编写的函数)</li></ol> <h4 id="信号相关函数"><a href="#信号相关函数" class="header-anchor">#</a> 信号相关函数</h4> <p><code>signal</code>函数:信号处理</p> <div class="language-c extra-class"><pre class="language-c"><code><span class="token keyword">void</span><span class="token punctuation">(</span><span class="token operator">*</span><span class="token function">signal</span><span class="token punctuation">(</span><span class="token keyword">int</span> sig<span class="token punctuation">,</span><span class="token keyword">void</span> <span class="token punctuation">(</span><span class="token operator">*</span>func<span class="token punctuation">)</span><span class="token punctuation">(</span><span class="token keyword">int</span><span class="token punctuation">)</span><span class="token punctuation">(</span><span class="token keyword">int</span><span class="token punctuation">)</span><span class="token punctuation">)</span><span class="token punctuation">)</span>
  148. </code></pre></div><blockquote><p><strong>sig</strong> 信号值</p> <p><strong>func</strong> 信号处理的函数指针,参数为信号值</p></blockquote> <p><code>sigaction</code>函数</p> <div class="language-c extra-class"><pre class="language-c"><code><span class="token keyword">int</span> <span class="token function">sigaction</span><span class="token punctuation">(</span><span class="token keyword">int</span> sig<span class="token punctuation">,</span><span class="token keyword">const</span> <span class="token keyword">struct</span> <span class="token class-name">sigaction</span> <span class="token operator">*</span>act<span class="token punctuation">,</span><span class="token keyword">struct</span> <span class="token class-name">sigaction</span> <span class="token operator">*</span>oact<span class="token punctuation">)</span>
  149. </code></pre></div><blockquote><p><strong>sig</strong> 信号值</p> <p><strong>act</strong> 指定信号的动作,相当于func</p> <p><strong>oact</strong> 保存原信号的动作</p></blockquote> <p><code>kill</code>函数</p> <p>把信号sig发送给pid进程,成功时返回0;当给定的信号无效、发送权限不够或目标进程不存在,则失败</p> <div class="language-c extra-class"><pre class="language-c"><code><span class="token keyword">int</span> <span class="token function">kill</span><span class="token punctuation">(</span><span class="token class-name">pid_t</span> pid<span class="token punctuation">,</span><span class="token keyword">int</span> sig<span class="token punctuation">)</span>
  150. </code></pre></div><blockquote><p><strong>pid</strong> 进程id</p> <p><strong>sig</strong> 信号值</p></blockquote> <p><code>alarm</code>函数</p> <p>提供一个闹钟的功能,进程可以调用alarm函数在经过预定时间时发送一个SIGALRM信号(定时信号)</p> <div class="language-c extra-class"><pre class="language-c"><code><span class="token keyword">unsigned</span> <span class="token keyword">int</span> <span class="token function">alarm</span><span class="token punctuation">(</span><span class="token keyword">unsigned</span> <span class="token keyword">int</span> seconds<span class="token punctuation">)</span>
  151. </code></pre></div><blockquote><p><strong>seconds</strong> 时间</p></blockquote> <h3 id="信号量"><a href="#信号量" class="header-anchor">#</a> 信号量</h3> <p>为了防止出现因多个程序同时访问一个共享资源而引发的一系列问题,我们需要一种方法,它可以通过生成并使用令牌来授权,在任一时刻只能有一个执行线程访问代码的临界区域。我们可以使用信号量。</p> <p>信号量本身只是一种外部资源的标识,不具有数据交换功能,而是通过控制其他的通信资源实现进程间通信。可以用来控制多个线程对共享资源的访问,亦或作为一种锁机制,防止某进程在访问资源时其它进程也访问该资源。因此,信号量主要责数据操作过程中的互斥,同步等功能。</p> <p>可以这样理解,信号量是一个计数器,当有进程对它所管理的资源进行请求时,进程先要读取信号量的值:若大于0,资源可以请求;若等于0,资源不可以用,这时进程会进入睡眠状态直至资源可用。当一个进程不再使用资源时,信号量+1(V操作),反之当有进程使用资源时,信号量-1(P操作)。对信号量的值操作均为原子操作。</p> <p>Linux提供了一组精心设计的信号量接口来对信号进行操作,不只是针对二进制信号量,另外,这些函数都是用来对成组的信号量值进行操作的。它们声明在头文件sys/sem.h中。</p> <div class="language-c extra-class"><pre class="language-c"><code><span class="token macro property"><span class="token directive-hash">#</span><span class="token directive keyword">include</span> <span class="token string">&lt;sys/sem.h&gt;</span></span>
  152. <span class="token comment">// 创建或获取一个信号量组:若成功返回信号量集ID,失败返回-1</span>
  153. <span class="token keyword">int</span> <span class="token function">semget</span><span class="token punctuation">(</span><span class="token class-name">key_t</span> key<span class="token punctuation">,</span> <span class="token keyword">int</span> num_sems<span class="token punctuation">,</span> <span class="token keyword">int</span> sem_flags<span class="token punctuation">)</span><span class="token punctuation">;</span>
  154. <span class="token comment">// 对信号量组进行操作,改变信号量的值:成功返回0,失败返回-1</span>
  155. <span class="token keyword">int</span> <span class="token function">semop</span><span class="token punctuation">(</span><span class="token keyword">int</span> semid<span class="token punctuation">,</span> <span class="token keyword">struct</span> <span class="token class-name">sembuf</span> semoparray<span class="token punctuation">[</span><span class="token punctuation">]</span><span class="token punctuation">,</span> <span class="token class-name">size_t</span> numops<span class="token punctuation">)</span><span class="token punctuation">;</span>
  156. <span class="token comment">// 控制信号量的相关信息</span>
  157. <span class="token keyword">int</span> <span class="token function">semctl</span><span class="token punctuation">(</span><span class="token keyword">int</span> semid<span class="token punctuation">,</span> <span class="token keyword">int</span> sem_num<span class="token punctuation">,</span> <span class="token keyword">int</span> cmd<span class="token punctuation">,</span> <span class="token punctuation">.</span><span class="token punctuation">.</span><span class="token punctuation">.</span><span class="token punctuation">)</span><span class="token punctuation">;</span>
  158. </code></pre></div><h3 id="消息队列"><a href="#消息队列" class="header-anchor">#</a> 消息队列</h3> <p>消息队列亦称报文队列,也叫做信箱。这种通信机制传递的数据具有某种结构,而不是简单的字节流。本质其实是一个内核提供的链表,内核基于这个链表,实现了一个数据结构,向消息队列中写数据,实际上是向这个数据结构中插入一个新结点;从消息队列汇总读数据,实际上是从这个数据结构中删除一个结点。</p> <p>消息队列克服了信号传递信息少,管道只能承载无格式字节流以及缓冲区大小受限等特点。对消息队列具有操作权限的进程可以使用函数完成对消息队列的操作控制。通过使用消息类型,进程可以按任何顺序读信息,或为消息安排优先级顺序。</p> <h4 id="消息队列相关函数"><a href="#消息队列相关函数" class="header-anchor">#</a> 消息队列相关函数</h4> <div class="language-c extra-class"><pre class="language-c"><code><span class="token macro property"><span class="token directive-hash">#</span><span class="token directive keyword">include</span> <span class="token string">&lt;sys/msg.h&gt;</span></span>
  159. <span class="token comment">// 创建消息队列: 成功将返回该消息队列的标识码;失败则返回 -1</span>
  160. <span class="token keyword">int</span> <span class="token function">msgget</span><span class="token punctuation">(</span><span class="token class-name">key_t</span> key<span class="token punctuation">,</span> <span class="token keyword">int</span> msgflg<span class="token punctuation">)</span><span class="token punctuation">;</span>
  161. <span class="token comment">// 添加信息到消息队列: 成功返回0,失败返回-1</span>
  162. <span class="token keyword">int</span> <span class="token function">msgsnd</span><span class="token punctuation">(</span><span class="token keyword">int</span> msgid<span class="token punctuation">,</span> <span class="token keyword">const</span> <span class="token keyword">void</span> <span class="token operator">*</span>msg_ptr<span class="token punctuation">,</span> <span class="token class-name">size_t</span> msg_sz<span class="token punctuation">,</span> <span class="token keyword">int</span> msgflg<span class="token punctuation">)</span><span class="token punctuation">;</span>
  163. <span class="token comment">// 从消息队列中读取消息: 成功返回实际放到接收缓冲区里去的字符个数失败,则返回 -1</span>
  164. <span class="token keyword">int</span> <span class="token function">msgrcv</span><span class="token punctuation">(</span><span class="token keyword">int</span> msgid<span class="token punctuation">,</span> <span class="token keyword">void</span> <span class="token operator">*</span>msg_ptr<span class="token punctuation">,</span> <span class="token class-name">size_t</span> msgsz<span class="token punctuation">,</span><span class="token keyword">long</span> <span class="token keyword">int</span> msgtype<span class="token punctuation">,</span> <span class="token keyword">int</span> msgflg<span class="token punctuation">)</span><span class="token punctuation">;</span>
  165. <span class="token comment">// 消息队列的控制函数: 成功返回0,失败返回-1</span>
  166. <span class="token keyword">int</span> <span class="token function">msgctl</span><span class="token punctuation">(</span><span class="token keyword">int</span> msqid<span class="token punctuation">,</span> <span class="token keyword">int</span> command<span class="token punctuation">,</span> strcut msqid_ds <span class="token operator">*</span>buf<span class="token punctuation">)</span><span class="token punctuation">;</span>
  167. </code></pre></div><h3 id="共享内存"><a href="#共享内存" class="header-anchor">#</a> 共享内存</h3> <p>共享内存就是映射一段能被其他进程所访问的内存,这段共享内存由一个进程创建,但多个进程都可以访问,一个进程写入共享内存的信息,可以被其他使用这个共享内存的进程,通过一个简单的内存读取错做读出,从而实现了进程间的通信。往往与其他通信机制,如信号量,配合使用。</p> <p>采用共享内存进行通信的一个主要好处是效率高,因为进程可以直接读写内存,而不需要任何数据的拷贝,对于像管道和消息队里等通信方式,则需要再内核和用户空间进行四次的数据拷贝,而共享内存则只拷贝两次:一次从输入文件到共享内存区,另一次从共享内存到输出文件。</p> <p>一般而言,进程之间在共享内存时,并不总是读写少量数据后就解除映射,而是保持共享区域,直到通信完毕为止。这样,数据内容一直保存在共享内存中,并没有写回文件。共享内存中的内容往往是在解除映射时才写回文件。</p> <h3 id="套接字"><a href="#套接字" class="header-anchor">#</a> 套接字</h3> <p>前面说到的进程间的通信,所通信的进程都是在同一台计算机上的,而使用socket进行通信的进程可以是同一台计算机的进程,也可以是通过网络连接起来的不同计算机上的进程。通常我们使用socket进行网络编程。</p> <p>socket,即套接字,是一种通信机制,凭借这种机制,客户/服务器系统的开发工作既可以在本地单机上进行,也可以跨网络进行。也就是说它可以让不在同一台计算机但通过网络连接计算机上的进程进行通信。也因为这样,套接字明确地将客户端和服务器区分开来。</p> <p>套接字的特性由3个属性确定:</p> <ol><li><strong>域</strong>:指定套接字通信中使用的网络介质,最常见的套接字域是AF_INET,它指的是Internet网络。</li> <li><strong>类型</strong>:因特网提供了两种通信机制:流(stream)和数据报(datagram),因而套接字的类型也就分为流套接字和数据报套接字。</li> <li><strong>协议</strong>:只要底层的传输机制允许不止一个协议来提供要求的套接字类型,我们就可以为套接字选择一个特定的协议。通常只需要使用默认值。</li></ol></div> <footer class="page-edit"><!----> <!----></footer> <!----> </main></div><div class="global-ui"></div></div>
  168. <script src="/OS_lab_tutorial/assets/js/app.de832b6b.js" defer></script><script src="/OS_lab_tutorial/assets/js/2.6cca19a7.js" defer></script><script src="/OS_lab_tutorial/assets/js/1.2e5d3cee.js" defer></script><script src="/OS_lab_tutorial/assets/js/26.7dca1b95.js" defer></script>
  169. </body>
  170. </html>