From: "ioquatix (Samuel Williams) via ruby-core" <ruby-core@...>
Date: 2024-11-20T08:59:24+00:00
Subject: [ruby-core:119974] [Ruby master Feature#19642] Remove vectored read/write from `io.c`.

Issue #19642 has been updated by ioquatix (Samuel Williams).

Status changed from Assigned to Closed

I am no longer planning to do this.

----------------------------------------
Feature #19642: Remove vectored read/write from `io.c`.
https://bugs.ruby-lang.org/issues/19642#change-110710

* Author: ioquatix (Samuel Williams)
* Status: Closed
* Assignee: ioquatix (Samuel Williams)
----------------------------------------
https://github.com/socketry/async/issues/228#issuecomment-1546789910 is a comment from the kernel developer who tells us that `writev` is always worse than `write` system call.

A large amount of complexity in `io.c` comes from optional support from `writev`.

So, I'd like to remove support for `writev`.

I may try to measure the performance before/after. However it may not show much difference, except that the implementation in `io.c` can be much simpler.



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/