[#107008] [Ruby master Bug#18465] Make `IO#write` atomic. — "ioquatix (Samuel Williams)" <noreply@...>
Issue #18465 has been reported by ioquatix (Samuel Williams).
16 messages
2022/01/09
[#107150] [Ruby master Feature#18494] [RFC] ENV["RUBY_GC_..."]= changes GC parameters dynamically — "ko1 (Koichi Sasada)" <noreply@...>
Issue #18494 has been updated by ko1 (Koichi Sasada).
4 messages
2022/01/17
[#107170] Re: [Ruby master Feature#18494] [RFC] ENV["RUBY_GC_..."]= changes GC parameters dynamically
— Eric Wong <normalperson@...>
2022/01/17
> https://bugs.ruby-lang.org/issues/18494
[#107302] [Ruby master Bug#18553] Memory leak on compiling method call with kwargs — "ibylich (Ilya Bylich)" <noreply@...>
Issue #18553 has been reported by ibylich (Ilya Bylich).
4 messages
2022/01/27
[#107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 — "mame (Yusuke Endoh)" <noreply@...>
Issue #18557 has been reported by mame (Yusuke Endoh).
18 messages
2022/01/29
[ruby-core:107057] Re: [Ruby master Bug#18465] Make `IO#write` atomic.
From:
Eric Wong <normalperson@...>
Date:
2022-01-11 17:20:03 UTC
List:
ruby-core #107057
"ioquatix (Samuel Williams)" <noreply@ruby-lang.org> wrote: > By the way, even calling `write` directly is no guarantee of > synchronous output between threads/processes - on Linux there > is an informal guarantee of page-sized atomicity. write(2) w/ O_APPEND on local FSes is atomic. Preforked servers (e.g. Apache) have been relying on that for decades to write log files. And PIPE_BUF for pipes/FIFOs is POSIX, (which equals page size on Linux). > Bug #18465: Make `IO#write` atomic. > https://bugs.ruby-lang.org/issues/18465#change-95859 Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>