From: Xiao-Yong Jin <meta.jxy@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] rconnect via aan reliability patch
Date: Tue, 31 Aug 2021 13:38:14 -0500 [thread overview]
Message-ID: <A47B3BB0-3545-4FD2-B24E-F0493C4A2426@gmail.com> (raw)
In-Reply-To: <41DB60AECD3C313EFF46C7CFB680A537@felloff.net>
Write does not block. Read does. In the case with read errors,
the aanserver end did everything before aanclient starts to read
the address, and somehow the channel has hung up before the read.
The extra read in aanserver blocks the aanserver at that point and
wait for the OK signal from aanclient before continuing.
The thing I don't understand is that what actually makes the channel
hang up. Do you have any suggestions as to how to debug this issue?
> On Aug 31, 2021, at 2:55 AM, cinap_lenrek@felloff.net wrote:
>
> how does this work? how is adding another roundtrip fixing
> a hung up tcp connection?
>
> the patch is probably fine, but i do not understand what it
> is fixing here...
>
> --
> cinap
next prev parent reply other threads:[~2021-09-01 1:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 22:24 Xiao-Yong Jin
2021-08-31 7:55 ` cinap_lenrek
2021-08-31 18:38 ` Xiao-Yong Jin [this message]
2021-09-01 1:20 ` cinap_lenrek
2021-09-06 14:58 ` mrowczok
2021-09-06 16:23 ` cinap_lenrek
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=A47B3BB0-3545-4FD2-B24E-F0493C4A2426@gmail.com \
--to=meta.jxy@gmail.com \
--cc=9front@9front.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.
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).