public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp•com>
To: David Miller <davem@davemloft•net>
Cc: nhorman@tuxdriver•com, netdev@vger•kernel.org, ilpo.jarvinen@helsinki•fi
Subject: Re: BSD 4.2 style TCP keepalives
Date: Wed, 06 Jan 2010 09:21:49 -0800	[thread overview]
Message-ID: <4B44C6AD.6040806@hp.com> (raw)
In-Reply-To: <20100105.195953.16499086.davem@davemloft.net>

David Miller wrote:
> From: Neil Horman <nhorman@tuxdriver•com>
> Date: Tue, 5 Jan 2010 21:07:56 -0500
> 
> 
>>Dave, If that patch fixes the problem (waiting on test results now,
>>but I figure it will), what if we add a parameter to tcp_sequence
>>(and tcp_validate_incomming), that represents an offset to trim from
>>end_seq (so that we can effectively ignore the garbage byte)?
> 
> 
> Sure, we could do that too, and it would be an improvement.
> 
> Let's first wait for test results and also give a bit for
> others to potentially come up with implementation ideas.

Might it suffice to simply enable TCP keepalives on the Linux end?  Or is that 
too big a kludge?

rick jones

  reply	other threads:[~2010-01-06 17:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06  0:39 BSD 4.2 style TCP keepalives David Miller
2010-01-06  2:07 ` Neil Horman
2010-01-06  3:59   ` David Miller
2010-01-06 17:21     ` Rick Jones [this message]
2010-01-06 20:50       ` Neil Horman
2010-01-06  8:23 ` David Miller
2010-01-06 23:04   ` David Miller
2010-01-07  0:14     ` David Miller
2010-01-07  3:21       ` David Miller
2010-01-07  3:36         ` David Miller
2010-01-07  0:34     ` Ilpo Järvinen
2010-01-07  0:59       ` David Miller
2010-01-07  7:55         ` Ilpo Järvinen
2010-01-08 12:40 ` Neil Horman
2010-01-08 21:21   ` David Miller
2010-01-09  1:22     ` Neil Horman
2010-01-09  1:41       ` David Miller

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=4B44C6AD.6040806@hp.com \
    --to=rick.jones2@hp$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=ilpo.jarvinen@helsinki$(echo .)fi \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=nhorman@tuxdriver$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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