Kernel-Kernel communication in a shared-memory multiprocessor:
Abstract: "In the standard kernel organization on a shared-memory multiprocessor all processors share the code and data of the operating system; explicit sychronization is used to control access to kernel data structures. Distributed-memory multicomputers use an alternative approach, in which e...
Gespeichert in:
| Format: | Buch |
|---|---|
| Sprache: | English |
| Veröffentlicht: |
Rochester, NY
1991
|
| Schriftenreihe: | University of Rochester <Rochester, NY> / Department of Computer Science: Technical report
368 |
| Schlagworte: | |
| Zusammenfassung: | Abstract: "In the standard kernel organization on a shared-memory multiprocessor all processors share the code and data of the operating system; explicit sychronization is used to control access to kernel data structures. Distributed-memory multicomputers use an alternative approach, in which each instance of the kernel performs local operations directly and uses remote invocation to perform remote operations. Either approach to inter-kernel communication can be used in a NonUniform Memory Access (NUMA) multiprocessor, although the performance tradeoffs may not be apparent in advance. In this paper we compare the use of remote access and remote invocation in the kernel of a NUMA multiprocessor operating system We discuss the issues and architectural features that must be considered when choosing an inter-kernel communication scheme, and describe a series of experiments on the BBN Butterfly designed to empirically evaluate the tradeoffs between remote invocation and remote memory access. We conclude that the Butterfly architecture is biased towards the use of remote invocation for most kernel operations, but that a small set of frequently executed operations can benefit from the use of remote access. |
| Beschreibung: | 12 S. |
Internformat
MARC
| LEADER | 00000nam a2200000 cb4500 | ||
|---|---|---|---|
| 001 | BV008974829 | ||
| 003 | DE-604 | ||
| 005 | 00000000000000.0 | ||
| 007 | t | ||
| 008 | 940206s1991 |||| 00||| eng d | ||
| 035 | |a (OCoLC)24448782 | ||
| 035 | |a (DE-599)BVBBV008974829 | ||
| 040 | |a DE-604 |b ger |e rakddb | ||
| 041 | 0 | |a eng | |
| 049 | |a DE-29T | ||
| 245 | 1 | 0 | |a Kernel-Kernel communication in a shared-memory multiprocessor |c Eliseu M. Chaves ... |
| 264 | 1 | |a Rochester, NY |c 1991 | |
| 300 | |a 12 S. | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b n |2 rdamedia | ||
| 338 | |b nc |2 rdacarrier | ||
| 490 | 1 | |a University of Rochester <Rochester, NY> / Department of Computer Science: Technical report |v 368 | |
| 520 | 3 | |a Abstract: "In the standard kernel organization on a shared-memory multiprocessor all processors share the code and data of the operating system; explicit sychronization is used to control access to kernel data structures. Distributed-memory multicomputers use an alternative approach, in which each instance of the kernel performs local operations directly and uses remote invocation to perform remote operations. Either approach to inter-kernel communication can be used in a NonUniform Memory Access (NUMA) multiprocessor, although the performance tradeoffs may not be apparent in advance. In this paper we compare the use of remote access and remote invocation in the kernel of a NUMA multiprocessor operating system | |
| 520 | 3 | |a We discuss the issues and architectural features that must be considered when choosing an inter-kernel communication scheme, and describe a series of experiments on the BBN Butterfly designed to empirically evaluate the tradeoffs between remote invocation and remote memory access. We conclude that the Butterfly architecture is biased towards the use of remote invocation for most kernel operations, but that a small set of frequently executed operations can benefit from the use of remote access. | |
| 650 | 4 | |a Multiprocessors | |
| 650 | 4 | |a Operating systems (Computers) | |
| 700 | 1 | |a Chaves, Eliseu M. |e Sonstige |4 oth | |
| 810 | 2 | |a Department of Computer Science: Technical report |t University of Rochester <Rochester, NY> |v 368 |w (DE-604)BV008902697 |9 368 | |
| 999 | |a oai:aleph.bib-bvb.de:BVB01-005926359 | ||
Datensatz im Suchindex
| _version_ | 1804123312912072704 |
|---|---|
| any_adam_object | |
| building | Verbundindex |
| bvnumber | BV008974829 |
| ctrlnum | (OCoLC)24448782 (DE-599)BVBBV008974829 |
| format | Book |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>02244nam a2200313 cb4500</leader><controlfield tag="001">BV008974829</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">00000000000000.0</controlfield><controlfield tag="007">t</controlfield><controlfield tag="008">940206s1991 |||| 00||| eng d</controlfield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)24448782</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV008974829</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">rakddb</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-29T</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Kernel-Kernel communication in a shared-memory multiprocessor</subfield><subfield code="c">Eliseu M. Chaves ...</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Rochester, NY</subfield><subfield code="c">1991</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">12 S.</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="b">n</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="b">nc</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="490" ind1="1" ind2=" "><subfield code="a">University of Rochester <Rochester, NY> / Department of Computer Science: Technical report</subfield><subfield code="v">368</subfield></datafield><datafield tag="520" ind1="3" ind2=" "><subfield code="a">Abstract: "In the standard kernel organization on a shared-memory multiprocessor all processors share the code and data of the operating system; explicit sychronization is used to control access to kernel data structures. Distributed-memory multicomputers use an alternative approach, in which each instance of the kernel performs local operations directly and uses remote invocation to perform remote operations. Either approach to inter-kernel communication can be used in a NonUniform Memory Access (NUMA) multiprocessor, although the performance tradeoffs may not be apparent in advance. In this paper we compare the use of remote access and remote invocation in the kernel of a NUMA multiprocessor operating system</subfield></datafield><datafield tag="520" ind1="3" ind2=" "><subfield code="a">We discuss the issues and architectural features that must be considered when choosing an inter-kernel communication scheme, and describe a series of experiments on the BBN Butterfly designed to empirically evaluate the tradeoffs between remote invocation and remote memory access. We conclude that the Butterfly architecture is biased towards the use of remote invocation for most kernel operations, but that a small set of frequently executed operations can benefit from the use of remote access.</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Multiprocessors</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Operating systems (Computers)</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Chaves, Eliseu M.</subfield><subfield code="e">Sonstige</subfield><subfield code="4">oth</subfield></datafield><datafield tag="810" ind1="2" ind2=" "><subfield code="a">Department of Computer Science: Technical report</subfield><subfield code="t">University of Rochester <Rochester, NY></subfield><subfield code="v">368</subfield><subfield code="w">(DE-604)BV008902697</subfield><subfield code="9">368</subfield></datafield><datafield tag="999" ind1=" " ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-005926359</subfield></datafield></record></collection> |
| id | DE-604.BV008974829 |
| illustrated | Not Illustrated |
| indexdate | 2024-07-09T17:27:47Z |
| institution | BVB |
| language | English |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-005926359 |
| oclc_num | 24448782 |
| open_access_boolean | |
| owner | DE-29T |
| owner_facet | DE-29T |
| physical | 12 S. |
| publishDate | 1991 |
| publishDateSearch | 1991 |
| publishDateSort | 1991 |
| record_format | marc |
| series2 | University of Rochester <Rochester, NY> / Department of Computer Science: Technical report |
| spelling | Kernel-Kernel communication in a shared-memory multiprocessor Eliseu M. Chaves ... Rochester, NY 1991 12 S. txt rdacontent n rdamedia nc rdacarrier University of Rochester <Rochester, NY> / Department of Computer Science: Technical report 368 Abstract: "In the standard kernel organization on a shared-memory multiprocessor all processors share the code and data of the operating system; explicit sychronization is used to control access to kernel data structures. Distributed-memory multicomputers use an alternative approach, in which each instance of the kernel performs local operations directly and uses remote invocation to perform remote operations. Either approach to inter-kernel communication can be used in a NonUniform Memory Access (NUMA) multiprocessor, although the performance tradeoffs may not be apparent in advance. In this paper we compare the use of remote access and remote invocation in the kernel of a NUMA multiprocessor operating system We discuss the issues and architectural features that must be considered when choosing an inter-kernel communication scheme, and describe a series of experiments on the BBN Butterfly designed to empirically evaluate the tradeoffs between remote invocation and remote memory access. We conclude that the Butterfly architecture is biased towards the use of remote invocation for most kernel operations, but that a small set of frequently executed operations can benefit from the use of remote access. Multiprocessors Operating systems (Computers) Chaves, Eliseu M. Sonstige oth Department of Computer Science: Technical report University of Rochester <Rochester, NY> 368 (DE-604)BV008902697 368 |
| spellingShingle | Kernel-Kernel communication in a shared-memory multiprocessor Multiprocessors Operating systems (Computers) |
| title | Kernel-Kernel communication in a shared-memory multiprocessor |
| title_auth | Kernel-Kernel communication in a shared-memory multiprocessor |
| title_exact_search | Kernel-Kernel communication in a shared-memory multiprocessor |
| title_full | Kernel-Kernel communication in a shared-memory multiprocessor Eliseu M. Chaves ... |
| title_fullStr | Kernel-Kernel communication in a shared-memory multiprocessor Eliseu M. Chaves ... |
| title_full_unstemmed | Kernel-Kernel communication in a shared-memory multiprocessor Eliseu M. Chaves ... |
| title_short | Kernel-Kernel communication in a shared-memory multiprocessor |
| title_sort | kernel kernel communication in a shared memory multiprocessor |
| topic | Multiprocessors Operating systems (Computers) |
| topic_facet | Multiprocessors Operating systems (Computers) |
| volume_link | (DE-604)BV008902697 |
| work_keys_str_mv | AT chaveseliseum kernelkernelcommunicationinasharedmemorymultiprocessor |