From: Eric Wong <e@80x24.org>
To: sleepy-penguin@bogomips.org
Subject: [PATCH] splice.c: remove reference to non-existent function
Date: Wed, 2 Jan 2019 20:50:33 +0000 [thread overview]
Message-ID: <20190102205033.19902-1-e@80x24.org> (raw)
There is no "trysplice" method, here. Instead, we rely on the
F_NONBLOCK and "exception: false" keyword argument.
---
ext/sleepy_penguin/splice.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/ext/sleepy_penguin/splice.c b/ext/sleepy_penguin/splice.c
index ab8c1ff..c9fe618 100644
--- a/ext/sleepy_penguin/splice.c
+++ b/ext/sleepy_penguin/splice.c
@@ -130,7 +130,6 @@ void sleepy_penguin_init_splice(void)
* out of them.
*
* It is highly recommended this flag be set
- * (or SleepyPenguin.trysplice used)
* whenever splicing from a socket into a pipe unless there is
* another (native) thread or process doing a blocking read on that
* pipe. Otherwise it is possible to block a single-threaded process
--
EW
reply other threads:[~2019-01-02 20:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/sleepy_penguin/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190102205033.19902-1-e@80x24.org \
--to=e@80x24.org \
--cc=sleepy-penguin@bogomips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/sleepy_penguin.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).