[#69616] [Ruby trunk - Feature #11258] add 'x' mode character for O_EXCL — cremno@...
Issue #11258 has been updated by cremno phobia.
3 messages
2015/06/16
[#69643] [Ruby trunk - Misc #11276] [RFC] compile.c: convert to use ccan/list — normalperson@...
Issue #11276 has been updated by Eric Wong.
3 messages
2015/06/17
[#69751] [Ruby trunk - Bug #11001] 2.2.1 Segmentation fault in reserve_stack() function. — kubo@...
Issue #11001 has been updated by Takehiro Kubo.
3 messages
2015/06/27
[ruby-core:69542] [Ruby trunk - Feature #11229] [PATCH] socket: allow exception-free nonblocking sendmsg/recvmsg
From:
matz@...
Date:
2015-06-12 08:53:00 UTC
List:
ruby-core #69542
Issue #11229 has been updated by Yukihiro Matsumoto. Looks good to me. Go ahead. Matz. ---------------------------------------- Feature #11229: [PATCH] socket: allow exception-free nonblocking sendmsg/recvmsg https://bugs.ruby-lang.org/issues/11229#change-52873 * Author: Eric Wong * Status: Open * Priority: Normal * Assignee: Yukihiro Matsumoto ---------------------------------------- As documented before, exceptions are expensive and IO::Wait*able are too common in socket applications to be the exceptional case. Datagram sockets deserve the same API which stream sockets are allowed with read_nonblock and write_nonblock. Note: this does not offer a performance advantage under optimal conditions when both ends are equally matched in speed, but it it does make debug output cleaner by avoiding exceptions whenever the receiver slows down. I think I have only one more change I'd like to add for recv/recvmsg* APIs in the future: destination buffers to reduce GC overhead ---Files-------------------------------- 0001-socket-allow-exception-free-nonblocking-sendmsg-recv.patch (13.4 KB) -- https://bugs.ruby-lang.org/