阻塞式IO是带限速的。比如nc从/dev/zero读取数据,然后写到某个socket,如果接收socket速度慢,那么从/dev/zero读取也会慢
thread per connection 适用于连接数较少,或者线程廉价的情况,对C++来说第二种情况不符合。
IO multiplexing 复用的不是IO而是线程,是同步方式而不是异步方式。
IO multiplexing 要与非阻塞IO配合使用,不能与阻塞IO配合使用,因为一旦某个socket fd 阻塞了,那么IO multiplexing所在的线程就被阻塞类,其他归该IO multiplexing 管理的socket fd也就被阻塞了。
那么在读取之前,先检查是否可读,是否就可以在IO复用线程中使用阻塞IO了呢?
答案是不可以,因为:
- accept : 当有客户端连接过来时,accept会返回listen fd 可读, 但是在”变得可读”和”accept”之间的这个时间窗口,客户端有可能已经close了。
- select: Under Linux, select() may report a socket file descriptor as “ready for reading”, while
nevertheless a subsequent read blocks. This could for example happen when data has arrived
but upon examination has wrong checksum and is discarded. There may be other circumstances
in which a file descriptor is spuriously reported as ready. Thus it may be safer to use
O_NONBLOCK on sockets that should not block. (即使告诉你可读,但是还是有可能block)