| B. N. Bershad, M. J. Zekauskas, and W. A. Sawdon. The Midway distributed shared memory system. In IEEE COMPCON, pages 528--537, February 1993. |
....invalidate protocol, which is similar to that used in many hardware or software based DSM (Distributed Shared Memory) systems. Researchers in computer architecture and DSM have been studying the cache coherence problem for a long time. Many concepts and theories such as several consistency models [35, 22, 16, 21, 7], and numerous practical systems such as the MIT Alewife [2] the Stanford Dash [36] CRL [30] and so on, have been developed to attack the problem. This problem is no different in the field of distributed virtual environments, so we simply borrow the idea from the DSM literature and modify it ....
.... accesses (both acquire and release accesses) are processor consistent with respect to one another [21] Entry consistency requires less communication bandwidth and permit even more concurrency by defining the owner of a synchronization variable as the processor that last acquired the variable [7]. A processor must request the ownership of a synchronization variable from its current owner before accessing the shared data guarded by the variable, and the current owner has the responsibility to ensure that all updates to the data guarded by the synchronization variable are then performed ....
[Article contains additional citation context not shown here]
Brian N. Bershad, Matthew J. Zekauskas, and Wayne A. Sawdon. The Midway distributed shared memory system. Proceedings of the 38th IEEE Computer Society International Conference (COMPCON'93), pages 528--537, February 1993. 111
.... page based DSM, followed by improvements such as Mirage [ea94] TreadMarks [ea96] or Odin [Pea96] Due to the possibility of false sharing, the performance of these systems strongly depends on the partitioning of data and the access characteristics of the distributed computation [BK98] Midway [BZS93] is not bound to HW pages. All store operations are performed through a library; no page faults are triggered. False sharing is circumvented but frequent writes degrade system performance. Munin [Car95] respects the size of individual objects, too and a different coherence protocol can be chosen ....
B. N. Bershad, M. J. Zekauskas, and W. A. Sawdon. The Midway distributed shared memory system. In IEEE COMPCON, pages 528--537, February 1993.
....To further improve parallel application performance, new consistency solutions were developed that reduced the amount of coordination and communication required among processors to keep shared memory consistent. A result of this effort was relaxed consistency models [CBZ91, ACD 96, JKW95, BZS93, Kel96] that employed techniques to combine shared memory writes or to delay when writes are seen by other processors. Relaxed consistency models also allowed DSM to hide some of the network latency. While relaxed consistency models allowed an application to compute the same results but with ....
....an application programmer must understand details about the application and how these details affect performance. Still, Eager Release Consistency often sends updates to processors that do not need them, causing both increased processor load and consumption of network resources. The Midway DSM [BZS93] uses an even more relaxed model called Entry Consistency. Entry Consistency requires a more detailed association between consistency and synchronization by requiring the application to bind each piece of shared data to a synchronization lock variable. The net effect reduces communication costs ....
[Article contains additional citation context not shown here]
Brian N. Bershad, Matthew J. Zekauskas, and Wayne A. Sawdon. The Midway distributed shared memory system. In Proceedings of the IEEE CompCon Conference, 1993.
....this problem fall into one of two extremes based on the amount of application knowledge they rely on. The first approach, typically adopted in parallel systems, is more or less transparent to the application developer, relying on application independent coherence schemes such as entry consistency [5,10,17,19] to guarantee that each object access sees consistent state. Coherence actions are triggered on demand, and, in the absence of knowledge about how the application accesses the object, tend to take conservative actions such as keeping the entire object state consistent after an update and or ....
.... a flat shared address space maintaining coherence either at fixed granularity or at variable granularity (objects) Example systems in the former category include TreadMarks [1] Shasta [18] and AURC [9] while those in the latter category include systems such as SharedRegions [17] Midway [5], SAM [19] and CRL [10] Recent research in both types of systems relies on the use of weak consistency protocols such as lazy release consistency [1] message driven release consistency [12] and entry consis1 Event services are sometimes also referred to as publishersubscriber systems [4] ....
[Article contains additional citation context not shown here]
B. N. Bershad, M. J. Zekauskas, and W. A. Sawdon. The Midway distributed shared memory system. In Proceedings of COMPCON 1993.
....known DSM system, JIAJIA, executing them on the same network, machines and operating systems, once they are evaluated under the same conditions, the results of this comparison would tend towards accurate comparisons. mario, geraldo) regulus.pcs.usp.br There are a few previous papers [3] 4] [9] compar ing different DSM systems; however, most of then do not evaluate DSM systems that belong to the second generation. One of the contributions of this paper is to show the speedups of two different scope DSM systems being executed on the same network of computers, because comparing ....
....generation. One of the contributions of this paper is to show the speedups of two different scope DSM systems being executed on the same network of computers, because comparing executions is more accurate and more correct than comparing simulations of the DSMs. In addition, as there are papers[3][9] that are using networks with different operating systems, to equalize the comparison, these two DSM systems are compared on a PC computer network with a free operating system. So, with an ordinary hardware, operating system, and DSMs system used throughout the academic community, it is guaranteed ....
Bershad B. N. , Zekauskas M. J. , SawDon W. A., The Midway Distributed Shared Memory System, COMPCOM 1993.
No context found.
B. N. Bershad, M. J. Zekauskas, and W. A. Sawdon. The Midway distributed shared memory system. In IEEE COMPCON, pages 528--537, February 1993.
No context found.
B. N. Bershad, M. J. Zekauskas, and W. A. Sawdon. The Midway distributed shared memory system. In IEEE COMPCON, pages 528--537, February 1993.
No context found.
Brian N. Bershad, Matthew J. Zekauskas, and Wayne A. Sawdon. The Midway distributed shared memory system. In Digest of Papers: COMPCON SPRING '93, pages 528--537, San Francisco, CA, February 1993.
No context found.
Bershad, B., Zekauskas, M., Sawdon, W. The Midway Distributed Shared Memory System. IEEE-COMPSAC 1993, 528537.
No context found.
B.N. Bershad, et al.: "The Midway Distributed Shared Memory System", In Proc. of IEEE COMPCON Conference, pp.528-537, 1993. 31
No context found.
B.N. Bershad, M.J. Zekauskas, and W.A. Sawdon. The Midway distributed shared memory system. In COMPCON, 1993.
No context found.
B. Bershad, M. Zekauskas, and W. Sawdon. The Midway distributed shared memory system. In Proc. of the 38th IEEE Int'l Computer Conf. (COMPCON Spring'93), pages 528--537, Feb. 1993.
No context found.
B. N. Bershad, M. J. Zekauskas, and W. A. Sawdon. The Midway distributed shared memory system. In Proc. of the 38th IEEE Int'l Computer Conf. (COMPCON Spring'93), pages 528--537, 1993.
No context found.
Bershad, B. N., Zekauskas, M. J. and Sawdon, W. A. (1993) The Midway distributed shared memory system. In The 38th IEEE Computer Society Int. Conf., pp. 528--537.
No context found.
B. N. Bershad, M. J. Zekauskas, and W. A. Sawdon. The Midway distributed shared memory system. In IEEE COMPCON, pages 528--537, February 1993.
No context found.
Bershad BN, Zekauskas MJ, Sawdom WA. The midway distributed shared memory system. IEEE International Computer 30 Conference (COMPCON'93), February 1993. http://www.cs.washington.edu/homes/bershad/Papers/.
No context found.
BERSHAD, B. N., ZEKAUSKAS, M. J., AND SAWDON, W. A. The Midway Distributed Shared memory System. In Proceedings IEEE COMPCON Conference (1993), IEEE, pp. 528--537.
No context found.
B. Bershad, M. Zekauskas and W. Sawdon, \The Midway Distributed Shared Memory System", Proceedings of COMPCOM '93, pp. 528-537, February, 1993.
No context found.
B.N. Bershad, M.J. Zekauskas, and W.A. Sawdon. The Midway distributed shared memory system. In Proceedings of the IEEE COMPCON '93 Conference, February 1993.
No context found.
Bershad B. N. , Zekauskas M. J., SawDon W. A., The Midway Distributed Shared Memory System , COMPCOM 1993.
No context found.
B. Bershad, M. Zekauskas, and W. Sawdon. The midway distributed shared memory system. In COMPCON Conference Proceedings, pages 528-537, 1993.
No context found.
B. N. Bershad, M. J. Zekauskas, and W. A. Sawdon. "The Midway Distributed Shared Memory System". In Proc. of the 38th IEEE Int'l Computer Conf. (COMPCON Spring'93), pp. 528-537, February 1993.
No context found.
Bershad, B., Zekauskas, M., Sawdon, W.: "The Midway distributed shared memory system"; Proc. IEEE COMPCON (1993), 528--537.
No context found.
B. N. Bershad, M. J. Zekauskas, and W. A. Sawdon. The Midway distributed shared memory system. In IEEE COMPCON, pages 528--537, February 1993.
No context found.
B. Bershad, M. Zekauskas and W. Sawdon (1993). The Midway distributed shared memory system. in Proceedings of the IEEE COMPCON.
First 50 documents Next 50
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC