• 主题
高级搜索  >
历史搜索 清空历史
首页> 外文期刊>Dr. Dobb's Journal >The Case for a Concurrency Platform
【24h】

The Case for a Concurrency Platform

机译：并发平台的案例

获取原文
获取原文并翻译 | 示例
           
页面导航
  • 摘要
  • 著录项
  • 相似文献
  • 相关主题

摘要

The advent of multicore processors is forcing software developers to explore multithreading. A critical decision is whether to "do it yourself" using POSIX threads (Pthreads) or WinAPI threads-which allow developers to directly manipulate operating-system threads-or to build atop a concurrency platform-a layer of software that coordinates, schedules, and manages the multicore resources. Concurrency platforms include any of various thread-pool libraries, such as .NET's ThreadPool class; message-passing libraries, such as MPI; data-parallel programming languages, such as NESL, RapidMind, and variants of Fortran since Fortran 90; task-parallel libraries, such as Intel's Threading Building Blocks (TBB) and Microsoft's Task Parallel Library (TPL); and parallel linguistic extensions, such as OpenMP and Cilk++. I submit that most applications would do better by adopting a concurrency platform than by using DIY multithreading. Over 100 interviews of prospective customers have led us at Cilk Arts to identify three key evaluation criteria on which customers refuse to compromise.
机译：多核处理器的出现迫使软件开发人员探索多线程。一个关键的决定是使用POSIX线程（Pthreads）还是WinAPI线程“自己动手”-允许开发人员直接操纵操作系统线程-还是在并发平台上构建–协调，计划和调度的软件层管理多核资源。并发平台包括各种线程池库中的任何一个，例如.NET的ThreadPool类。消息传递库，例如MPI；数据并行编程语言，例如NESL，RapidMind，以及Fortran 90以后的Fortran变体；任务并行库，例如英特尔的线程构建模块（TBB）和微软的任务并行库（TPL）；以及并行语言扩展，例如OpenMP和Cilk ++。我认为，大多数应用程序通过采用并发平台要比使用DIY多线程更好。超过100次对潜在客户的采访使我们在Cilk Arts找出了三个拒绝客户妥协的关键评估标准。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱：kefu@zhangqiaokeyan.com

京公网安备：11010802029741号 ICP备案号：京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有

  • 客服微信

  • 服务号