All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Lehan <krellan@krellan.com>
To: "Marcus D. Leech" <mleech@ripnet.com>
Cc: Josh Lehan <linux@krellan.com>, netdev@vger.kernel.org
Subject: Re: Skipping past TCP lost packet in userspace
Date: Mon, 30 May 2011 21:12:00 -0700	[thread overview]
Message-ID: <4DE46A90.6080004@krellan.com> (raw)
In-Reply-To: <4DE460E1.5020103@ripnet.com>

On 05/30/2011 08:30 PM, Marcus D. Leech wrote:
> This sounds like you want UDP, not TCP.
> 
> Unless I'm misunderstanding what you want, you want a protocol that has
> a different "contract"
>   than TCP.  Doing what you want basically requires breaking TCP.  That
> isn't going to happen.

Thanks.  This wouldn't break the TCP protocol on the wire, though.
Instead, it would merely provide a way for a userspace application to
"peek" at the arrived data that's behind the missing packet.  There's
already an ioctl() to peek at unread data, but it considers the missing
packet to be a barrier, and will not allow the application to see beyond it.

The reason for TCP is for maximum compatibility with firewalls, proxies,
and all the other annoyances of the modern commercialized Internet.
Using UDP would indeed solve this problem, but defeat the point of being
compatible.  Using other exotic protocols such as SCTP or DCCP is a
nonstarter.

Josh Lehan

  reply	other threads:[~2011-05-31  5:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31  1:19 Skipping past TCP lost packet in userspace Josh Lehan
2011-05-31  3:30 ` Marcus D. Leech
2011-05-31  4:12   ` Josh Lehan [this message]
2011-05-31  4:05 ` Mikael Abrahamsson
2011-05-31 11:12 ` Neil Horman
2011-05-31 17:23 ` Yuchung Cheng
2011-06-01  8:10   ` Josh Lehan
2011-06-01 16:57     ` Bill Sommerfeld
2011-06-01 17:35     ` Rick Jones
2011-06-24 14:58       ` Janardhan Iyengar
2011-06-30  8:38         ` Josh Lehan
2011-06-30 14:36           ` Neil Horman
2011-07-01  8:39             ` Josh Lehan
2011-07-01 13:37               ` Neil Horman
2011-06-01 19:36     ` juice
2011-06-03 11:51     ` Ilpo Järvinen
2011-06-06  6:30       ` Josh Lehan

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=4DE46A90.6080004@krellan.com \
    --to=krellan@krellan.com \
    --cc=linux@krellan.com \
    --cc=mleech@ripnet.com \
    --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 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.