{"title":"蜜汁通信处理器的分析","authors":"P. Steenkiste","doi":"10.1109/HPCS.1992.759112","DOIUrl":null,"url":null,"abstract":"Nectar is a multicomputer built around a high-bandwidth crosspoint network. Nodes are connected to Nectar using network coprocessors (CABs) that do the protocol processing. The communication coprocessor is based on a general-purpose processor and runs a flexible runtime system. This allows us to offload application on the coprocessor and to experiment with different protocol implementations. An important network parameter for applications is the latency for short messages. In this paper we present an analysis of the CAB-CAB and host-host communication latency over Nectar for a number of communication protocols. We break up the latency and discuss how the components an influenced by the protocol implementation and node architecture.","PeriodicalId":274790,"journal":{"name":"IEEE Workshop on the Architecture and Implementation of High Performance Communication Subsystems","volume":"5 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1992-02-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"12","resultStr":"{\"title\":\"Analysis of the Nectar Communication Processor\",\"authors\":\"P. Steenkiste\",\"doi\":\"10.1109/HPCS.1992.759112\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Nectar is a multicomputer built around a high-bandwidth crosspoint network. Nodes are connected to Nectar using network coprocessors (CABs) that do the protocol processing. The communication coprocessor is based on a general-purpose processor and runs a flexible runtime system. This allows us to offload application on the coprocessor and to experiment with different protocol implementations. An important network parameter for applications is the latency for short messages. In this paper we present an analysis of the CAB-CAB and host-host communication latency over Nectar for a number of communication protocols. We break up the latency and discuss how the components an influenced by the protocol implementation and node architecture.\",\"PeriodicalId\":274790,\"journal\":{\"name\":\"IEEE Workshop on the Architecture and Implementation of High Performance Communication Subsystems\",\"volume\":\"5 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1992-02-17\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"12\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"IEEE Workshop on the Architecture and Implementation of High Performance Communication Subsystems\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/HPCS.1992.759112\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"IEEE Workshop on the Architecture and Implementation of High Performance Communication Subsystems","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/HPCS.1992.759112","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Nectar is a multicomputer built around a high-bandwidth crosspoint network. Nodes are connected to Nectar using network coprocessors (CABs) that do the protocol processing. The communication coprocessor is based on a general-purpose processor and runs a flexible runtime system. This allows us to offload application on the coprocessor and to experiment with different protocol implementations. An important network parameter for applications is the latency for short messages. In this paper we present an analysis of the CAB-CAB and host-host communication latency over Nectar for a number of communication protocols. We break up the latency and discuss how the components an influenced by the protocol implementation and node architecture.