多个 ASIO io_service 是一件好事吗？
我已经开始使用 Boost.ASIO 进行一些简单的网络编程，我对这个库的理解不是很多，所以请耐心等待我和我的新手问题。
目前，在我的项目中，我只有 1 个 io_service 对象。用于所有异步 I/O 操作等。
我的理解是，可以创建多个线程并将 io_service 实例的 run 方法传递给线程，以便为 io_service 提供更多线程。
我的问题：拥有多个 io_service 对象是一个好的设计吗？例如，有 2 个不同的 io_service 实例，每个实例都有 2 个关联的线程，它们是否以某种方式相互了解（并因此相互合作），或者如果不了解，它们是否会对彼此产生负面影响？
我的目的是拥有 1 个 io_service 用于基于套接字的 I/O，另一个用于基于串行 (tty) I/O。
I've begun using Boost.ASIO for some simple network programming, my understanding of the library is not a great deal, so please bear with me and my newbie question.
At the moment in my project I only have 1 io_service object. Which use for all the async I/O operations etc.
My understanding is that one can create multiple threads and pass the run method of an io_service instance to the thread to provide more threads to the io_service.
My question: Is it good design to have multiple io_service objects? say for example have 2 distinct io_service instances, each with 2 threads associated, do they somehow know about each other (and hence cooperate with each), or if not would they negatively affect each other?
My intention is to have 1 io_service for socket based I/O and another for serial based (tty) I/O.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我们使用多个 io_service 是因为应用程序中的某些组件需要以特定的固定优先级运行其所有工作线程，每个组件的优先级不同。因此，每个组件都有自己的 io_service，并且每个组件都有自己的执行 run() 的线程池。
我能想到的其他设计是，每个 IO 是否需要池中不同数量的线程，或者，与您的情况更相关的是，如果池无法共享，因为例如，如果您的网络 IO 可以取出每个线程并让串行 IO 等待。
We use multiple io_service's because some of the components in our application need to run all their worker threads at certain fixed priorities, different for each component. Thus each component is given its own io_service, and each component has its own pool of threads executing
run().Other designs I could think of would be if a different number of threads in the pool is required for each IO, or, more relevant to your case, is if the pool cannot be shared because, for example, if your network IO can take out every thread and leave your serial IO waiting.
IIRC，在 Michael Caisse 的 Boostcon ASIO 演讲期间（无论如何值得观看），我相信这个问题是由一位观众明确提出的，并被认为是一个潜在的解决方案。我从中得出，它本身并没有错，并且可以根据您的设计以这种方式使用。
IIRC, during Michael Caisse's Boostcon ASIO talk (which is worth watching anyway), I believe this question is explicitly asked by an audience member and ok'd as a potential solution. I take from that that it's not wrong per se, and can be used that way according to your design.
此讨论可能具有启发性：
http://thread.gmane.org /gmane.comp.lib.boost.asio.user/1300
This discussion may be enlightening:
http://thread.gmane.org/gmane.comp.lib.boost.asio.user/1300