From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] Doesn't 'close' call finish pending 'read' on the same 'fd'?
Date: Thu, 13 Nov 2014 14:37:12 +0100 [thread overview]
Message-ID: <2ef336f7e8e64f4698f9e00e62adb0a5@felloff.net> (raw)
In-Reply-To: <CAGNd-2PG0taXB=nR_UKi8QQoo4CX0kbML1BmqJ9z=4qQsCJv3Q@mail.gmail.com>
interesting, that might be worth implementing.
the alternative would be to send the reading process a note to
interrupt the blocking syscall.
the closer proc should just send the note and not close the fd.
and the reader proc should close the fd once he's out of the
reading loop.
--
cinap
next prev parent reply other threads:[~2014-11-13 13:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 12:21 Pavel Klinkovský
2014-11-13 12:43 ` cinap_lenrek
2014-11-13 12:49 ` Pavel Klinkovský
2014-11-13 13:08 ` cinap_lenrek
2014-11-13 13:13 ` Pavel Klinkovský
2014-11-13 13:17 ` cinap_lenrek
2014-11-13 13:20 ` Pavel Klinkovský
2014-11-13 13:37 ` cinap_lenrek [this message]
2014-11-13 13:45 ` Pavel Klinkovský
2014-11-13 14:43 ` cinap_lenrek
2014-11-13 14:50 ` Pavel Klinkovský
2014-11-13 15:35 ` Pavel Klinkovský
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2ef336f7e8e64f4698f9e00e62adb0a5@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9fans@9fans.net \
/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.
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 NNTP newsgroup(s).