here - Stefan-Marr.de

More documents

Recommendations

Info

9. Conclusion and Future Work 9.1. Problem and Thesis Statement Revisited This dissertation set out to address the problem of today’s virtual machines not reconciling the trend for increased hardware parallelism, which is the result of the multicore revolution, with the trend of using VMs as general purpose platforms with a wide variety of languages. Today, language and library implementers struggle to build concurrent programming concepts on top of multi-language VMs, because these VMs do not provide the necessary abstractions. Hence, the objective of this dissertation is to find a solution for the insufficient support for concurrent and parallel programming in VMs. Since today’s VMs support only a limited range of concurrent and parallel programming concepts, first needed to be identified the concepts that would benefit from VM support for improved performance or enforcement of semantics. Initially the problem was that the set of abstractions required from a VM was unknown. With these problems in mind, the following thesis statement was formulated: There exists a relevant and significant subset of concurrent and parallel programming concepts that can be realized on top of a unifying substrate. This substrate enables the flexible definition of language semantics, which build on the identified set of concepts, and this substrate lends itself to an efficient implementation. Three concrete research goals were derived from the thesis statement: Identify a Set of Requirements The first goal of this research was to understand how concurrent and parallel programming are supported in today’s VMs and how the underlying programming concepts relate to each other. Chapter 3 approached this goal with a survey and concluded that concepts for parallel programming benefit mainly from support for optimization in a VM, and that concepts for concurrent programming require support for their semantics. Since these two concerns are largely orthogonal, this dissertation chose to focus on concepts for concurrent programming. Chapter 3 further discussed a number of problems language implementers face today and derived a set of requirements for their support in multi-language VMs. Define a Unifying Substrate The second research goal was to identify a unifying substrate to support concurrent programming concepts. Based on 236
9.2. Contributions the identified requirements, this dissertation proposes an ownershipbased metaobject protocol (OMOP) in Chapter 5. Demonstrate Applicability The third and final research goal was to demonstrate the applicability of the proposed OMOP. On the one hand, Chapter 6 needed to evaluate the OMOP’s capabilities as a unifying substrate. Thus, it needed to demonstrate that the OMOP facilitates the implementation of a wide range of concepts for concurrent programming. On the other hand, in Chapter 8 it was the goal to show that the OMOP gives rise to an efficient implementation. Thus, the evaluation needed to show that by using the OMOP it is possible to implement concepts for concurrent programming in a way that their performance is on par with conventional implementations. Two prototypes of the OMOP were implemented to support the thesis statement and to achieve the research goals. The first implementation uses AST transformation on top of an unchanged VM. The second implementation adapts the bytecode semantics of an existing VM. Based on these implementations, Chapter 6 evaluated the OMOP and Chapter 8 demonstrated its applicability. 9.2. Contributions This section recapitulates the main chapters of this dissertation so as to identify the individual contributions of each of them. • Chapter 2 discusses the widespread use of VMs as general purpose platforms and identifies the need for a unifying abstractions to avoid complex feature interaction in VMs that hinder extensibility and maintainability. Furthermore, it revisits the reasons for the multicore revolution and concludes that software developers need to pursue parallelism to achieve the performance required for their applications. The vision of this dissertation is that applications are built using the appropriate concurrent and parallel programming techniques for, e. g., user interface and data processing. Moreover, the chapter defines the notions of concurrent programming and parallel programming to enable a categorization of the corresponding programming concepts based on their intent. 237
Page 1 and 2:
Faculty of Science and Bio-Engineer
Page 3:
DON’T PANIC
Page 7:
S A M E N VAT T I N G Over de laats
Page 11 and 12:
C O N T E N T S 1. Introduction 1 1
Page 13 and 14:
Contents 4.4. RoarVM . . . . . . .
Page 15:
Contents 9.5. Future Work . . . . .
Page 19:
L I S T O F TA B L E S 2.1. Flynn
Page 22 and 23:
List of Listings 7.2. Applying tran
Page 24 and 25:
1. Introduction of solutions for di
Page 26 and 27:
1. Introduction traded in for bette
Page 28 and 29:
1. Introduction ad hoc implementati
Page 30 and 31:
1. Introduction Chapter 7: Implemen
Page 32 and 33:
1. Introduction and systems [De Kos
Page 34 and 35:
1. Introduction ReBench This disser
Page 36 and 37:
2. Context and Motivation 2.1. Mult
Page 38 and 39:
2. Context and Motivation in litera
Page 40 and 41:
2. Context and Motivation e. g., ar
Page 42 and 43:
2. Context and Motivation tasks wit
Page 44 and 45:
2. Context and Motivation section.
Page 46 and 47:
2. Context and Motivation Table 2.1
Page 48 and 49:
2. Context and Motivation The remai
Page 50 and 51:
2. Context and Motivation Clojure A
Page 52 and 53:
2. Context and Motivation To achiev
Page 54 and 55:
2. Context and Motivation Each vat
Page 56 and 57:
2. Context and Motivation driven to
Page 58 and 59:
2. Context and Motivation 2.5. Buil
Page 60 and 61:
2. Context and Motivation First, it
Page 62 and 63:
3. Which Concepts for Concurrent an
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 111 and 112:
4 E X P E R I M E N TAT I O N P L A
Page 113 and 114:
4.2. SOM: Simple Object Machine SOM
Page 115 and 116:
4.2. SOM: Simple Object Machine 1 S
Page 117 and 118:
4.2. SOM: Simple Object Machine nee
Page 119 and 120:
4.2. SOM: Simple Object Machine 1 S
Page 121 and 122:
4.2. SOM: Simple Object Machine HAL
Page 123 and 124:
4.4. RoarVM Used Software and Libra
Page 125 and 126:
4.4. RoarVM that is performance cri
Page 127 and 128:
4.4. RoarVM Table 4.2.: The Smallta
Page 129 and 130:
4.4. RoarVM is a problematic operat
Page 131 and 132:
5 A N O W N E R S H I P - B A S E D
Page 133 and 134:
5.1. Open Implementations and Metao
Page 135 and 136:
5.2. Design of the OMOP metaclass-b
Page 137 and 138:
5.2. Design of the OMOP Meta Level
Page 139 and 140:
5.2. Design of the OMOP set of mech
Page 141 and 142:
5.3. The OMOP By Example current :
Page 143 and 144:
5.3. The OMOP By Example dling writ
Page 145 and 146:
5.3. The OMOP By Example The proces
Page 147 and 148:
5.4. Semantics of the MOP 1 SOMObje
Page 149 and 150:
5.4. Semantics of the MOP 1 SOMInte
Page 151 and 152:
5.5. Customizations and VM-specific
Page 153 and 154:
5.6. Related Work how to use it to
Page 155 and 156:
5.6. Related Work In ABCL/R2, meta-
Page 157:
5.7. Summary which owns a set of ob
Page 160 and 161:
6. Evaluation: The OMOP as a Unifyi
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 203 and 204:
7 I M P L E M E N TAT I O N A P P R
Page 205 and 206:
7.1. AST Transformation VMs makes s
Page 207 and 208: 7.1. AST Transformation all have th
Page 209 and 210: 7.1. AST Transformation because thi
Page 211 and 212: 7.2. Virtual Machine Support ments
Page 213 and 214: 7.2. Virtual Machine Support to the
Page 215 and 216: 7.2. Virtual Machine Support 1 void
Page 217 and 218: 7.2. Virtual Machine Support 1 void
Page 219 and 220: 7.2. Virtual Machine Support Table
Page 221: 7.3. Summary the RoarVM, primitives
Page 224 and 225: 8. Evaluation: Performance 8.1. Eva
Page 226 and 227: 8. Evaluation: Performance tional c
Page 228 and 229: 8. Evaluation: Performance The goal
Page 230 and 231: 8. Evaluation: Performance benchmar
Page 232 and 233: 8. Evaluation: Performance General
Page 234 and 235: 8. Evaluation: Performance Runtime
Page 236 and 237: 8. Evaluation: Performance 1.10 1.0
Page 238 and 239: 8. Evaluation: Performance all OMOP
Page 240 and 241: 8. Evaluation: Performance 31.62 Am
Page 242 and 243: 8. Evaluation: Performance Runtime,
Page 252 and 253: 8. Evaluation: Performance hide inh
Page 254 and 255: 8. Evaluation: Performance Conclusi
Page 256 and 257: 8. Evaluation: Performance improve
Page 260 and 261: 9. Conclusion and Future Work • C
Page 262 and 263: 9. Conclusion and Future Work A sol
Page 264 and 265: 9. Conclusion and Future Work The p
Page 266 and 267: 9. Conclusion and Future Work the a
Page 268 and 269: 9. Conclusion and Future Work all r
Page 271 and 272: A A P P E N D I X : S U RV E Y M AT
Page 273 and 274: A.1. VM Support for Concurrent and
Page 275 and 276: A.1. VM Support for Concurrent and
Page 277 and 278: A.2. Concurrent and Parallel Progra
Page 283 and 284: B A P P E N D I X : P E R F O R M A
Page 285 and 286: B.1. Benchmark Characterizations LR
Page 287 and 288: B.1. Benchmark Characterizations We
Page 289 and 290: B.2. Benchmark Configurations B.2.
Page 291: B.2. Benchmark Configurations 101 p
Page 294 and 295: References Joe Armstrong. A history
Page 296 and 297: References Zoran Budimlic, Aparna C
Page 298 and 299: References Koen De Bosschere. Proce
Page 300 and 301: References Yaoqing Gao and Chung Kw
Page 302 and 303: References Michael Haupt, Stefan Ma
Page 304 and 305: References ISO. ISO/IEC 14882:2011
Page 306 and 307: References Tim Lindholm, Frank Yell
Page 308 and 309:
References on Modularity In Systems
Page 310 and 311:
References Johan Östlund, Tobias W
Page 312 and 313:
References Tardieu. The asynchronou
Page 314 and 315:
References Matthew J. Sottile, Timo
Page 316 and 317:
References ming in mobile ad hoc ne
Page 318:
References 3-14, New York, NY, USA,
show all

here - Stefan-Marr.de

Create successful ePaper yourself

Delete template?

Save as template?