From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <2ef336f7e8e64f4698f9e00e62adb0a5@felloff.net> References: <2ef336f7e8e64f4698f9e00e62adb0a5@felloff.net> Date: Thu, 13 Nov 2014 14:45:18 +0100 Message-ID: From: =?UTF-8?Q?Pavel_Klinkovsk=C3=BD?= To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11351efa14b7750507bdb92e Subject: Re: [9fans] Doesn't 'close' call finish pending 'read' on the same 'fd'? Topicbox-Message-UUID: 273f02d8-ead9-11e9-9d60-3106f5b1d025 --001a11351efa14b7750507bdb92e Content-Type: text/plain; charset=UTF-8 > interesting, that might be worth implementing. > Maybe. > the alternative would be to send the reading process a note to > interrupt the blocking syscall. > Actually, it my 'plan B'... ;) 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. > Exactly! Well, I would prefer a solution with 'hangup', it seems cleaner to me... ...but since it is not implemented in UDP driver, I will implement the note based solution. Pavel Pavel --001a11351efa14b7750507bdb92e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

=
interesting, that might be worth implementin= g.

Maybe.
=C2=A0
the alternative would be to send the reading proces= s a note to
interrupt the blocking syscall.

Actuall= y, it my 'plan B'... ;)=C2=A0

the closer proc should just send the note and not close the f= d.
and the reader proc should close the fd once he's out of the
reading loop.

Exactly!

Well, I would prefer a solution with 'hangup', it seems cl= eaner to me...
...but since it is not implemented in UDP driver, = I will implement the note based solution.

Pavel


Pavel
--001a11351efa14b7750507bdb92e--