From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
Adam Langley <agl@imperialviolet.org>,
netdev@vger.kernel.org
Subject: Re: How I can reset TCP sockets after long suspend/resume cyscle
Date: Fri, 6 Jun 2008 00:31:16 +0300 [thread overview]
Message-ID: <200806060031.16827.maximlevitsky@gmail.com> (raw)
In-Reply-To: <484707D9.3040900@hp.com>
On Thursday, 5 June 2008 00:23:37 Rick Jones wrote:
> > Another idea would be for the kernel to prematurely run the keepalive
> > timer for all TCP connections after resume. The keepalive code would send
> > an ACK (out of window) which causes other side to send a RST or ACK.
> >
> > It is normal behaviour, the change would just make the timer happen sooner.
>
> Would you have it done even for those endpoints on which SO_KEEPALIVE
> wasn't set?
Why not?
This seems the right solution,
if this is possible, why not to check for stuck TCP connections
on resume?
Obviously, we should be able to turn this off, for some reasons, maybe some
weird servers, but generally this can be the default.
>
> rick jones
>
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2008-06-05 21:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 12:15 How I can reset TCP sockets after long suspend/resume cyscle Maxim Levitsky
2008-06-04 15:34 ` Maxim Levitsky
2008-06-04 16:09 ` Adam Langley
2008-06-04 16:21 ` Stephen Hemminger
2008-06-04 21:00 ` Maxim Levitsky
2008-06-04 21:02 ` Rick Jones
2008-06-04 20:52 ` Maxim Levitsky
2008-06-04 21:15 ` Stephen Hemminger
2008-06-04 21:23 ` Rick Jones
2008-06-05 21:31 ` Maxim Levitsky [this message]
2008-06-05 21:50 ` Rick Jones
2008-06-06 8:37 ` Benny Amorsen
2008-06-06 9:27 ` Nadejda Levitsky
2008-06-05 7:13 ` Evgeniy Polyakov
2008-06-05 21:19 ` Maxim Levitsky
2008-06-05 22:20 ` Evgeniy Polyakov
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=200806060031.16827.maximlevitsky@gmail.com \
--to=maximlevitsky@gmail.com \
--cc=agl@imperialviolet.org \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=shemminger@vyatta.com \
/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).