From: Jamie Gloudon <jamie.gloudon@gmail.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: Eric Dumazet <erdnetdev@gmail.com>, netdev@vger.kernel.org
Subject: Re: Is keepalive behaving as expected in 3.7.0+/net-next?
Date: Sun, 30 Dec 2012 21:50:09 -0400 [thread overview]
Message-ID: <50e0ef55.11f2640a.4ef8.ffffd018@mx.google.com> (raw)
In-Reply-To: <50E0A963.6080900@hp.com>
On Sun, Dec 30, 2012 at 12:51:47PM -0800, Rick Jones wrote:
> >Make a lot of sense. However, I got the impression from Rick that
> >having tcp_keepalive_intvl > tcp_keepalive_time behaved correctly in
> >older versions of the kernel.
>
> I seek to make no assertions about the behaviour of older kernels. I was
> just going off the ip-sysctl.txt wording I was looking to clean-up.
>
> rick
Ok, should ip-sysctl.txt documentation be updated to warn not to set tcp_keepalive_intvl > tcp_keepalive_time?
Regards,
Jamie Gloudon
next prev parent reply other threads:[~2012-12-31 2:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 22:05 Is keepalive behaving as expected in 3.7.0+/net-next? Rick Jones
2012-12-27 21:54 ` Eric Dumazet
2012-12-29 19:47 ` Jamie Gloudon
2012-12-30 20:51 ` Rick Jones
2012-12-31 1:50 ` Jamie Gloudon [this message]
2013-01-03 20:13 ` Rick Jones
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=50e0ef55.11f2640a.4ef8.ffffd018@mx.google.com \
--to=jamie.gloudon@gmail.com \
--cc=erdnetdev@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.