From: Andi Kleen <andi@firstfloor.org>
To: <Li_Xin2@emc.com>
Cc: <linux-kernel@vger.kernel.org>, netdev@vger.kernel.org
Subject: Re: TCP keepalive timer problem
Date: Tue, 25 Aug 2009 16:04:54 +0200 [thread overview]
Message-ID: <87fxbgf0qh.fsf@basil.nowhere.org> (raw)
In-Reply-To: <0939B589FC103041945B9F13274963E303B1A9D4@CORPUSMX90A.corp.emc.com> (Li Xin2's message of "Tue, 25 Aug 2009 04:32:45 -0400")
<Li_Xin2@emc.com> writes:
[cc netdev]
> Greetings,
>
> I found one problem in Linux TCP keepalive timer processing, after
> searching on google, I found Daniel Stempel reported the same problem in
> 2007 (http://lkml.indiana.edu/hypermail/linux/kernel/0702.2/1136.html),
> but got no answer. So I have to reraise it.
>
> Can anyone help answer this two-years long question?
I think the idea behind the tcp_keepalive_timer check referrenced in the
other mail is: when there are outstanding non acked packets then
the normal retransmit timer will do keep alive because it will
retransmit and retransmit in exponential backoff and eventually notice
something is wrong.
The obvious hole is that if the keepalive is shorter than the worst
case retransmit timeout then you'll have to wait for the longer
timeout. I presume that's what is happening for you? You set the
keep alive timeout very low and expect the timeout to be very low,
but it's 30+mins (default retransmit timeout)?
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2009-08-25 14:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0939B589FC103041945B9F13274963E303B1A9D4@CORPUSMX90A.corp.emc.com>
2009-08-25 13:13 ` TCP keepalive timer problem Eric Dumazet
2009-08-25 14:05 ` Li_Xin2
2009-08-27 12:45 ` Eric Dumazet
2009-08-27 13:35 ` Andi Kleen
2009-08-27 14:17 ` Eric Dumazet
2009-08-27 14:29 ` Andi Kleen
2009-08-27 14:49 ` Eric Dumazet
2009-08-28 1:55 ` Li_Xin2
2009-08-28 7:05 ` Damian Lukowski
2009-08-25 14:04 ` Andi Kleen [this message]
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=87fxbgf0qh.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=Li_Xin2@emc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).