netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Werner Almesberger <werner@almesberger.net>
To: Sridhar Samudrala <sri@us.ibm.com>
Cc: Suparna Bhattacharya <suparna@in.ibm.com>, netdev@oss.sgi.com
Subject: Re: net-AIO and real-time TCP (blue sky research)
Date: Wed, 11 Aug 2004 21:40:44 -0300	[thread overview]
Message-ID: <20040811214044.U28020@almesberger.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0408111643460.3103@localhost.localdomain>; from sri@us.ibm.com on Wed, Aug 11, 2004 at 04:44:04PM -0700

Sridhar Samudrala wrote:
> Your AIO-TCP looks pretty similar to the partial reliablity extension to
> SCTP that allows an SCTP endpoint to signal to its peer that it is no longer
> going to retransmit certain messages and should skip past those messages.

Damn, so it's not such a crazy idea after all :-)

Something like this would be useful for the sender side, if the
receiver can't figure out on its own that it shouldn't wait for
the data to arrive. (And, assuming that the sender skips data by
leaving a gap, not by filling it with other data, which seems
like a reasonable assumption if we use AIO-TCP at both ends. If
the receiver may use regular TCP, the sender would have to try
to fill the missing part, which can be hairy, particularly if
some of the data-to-be-dropped has already be sent.)

Clearly, any such thing on the sender side would need to have some
means to detect that the receiver can recover from segments that
are never sent.

Is a concrete API for this functionality described somewhere ?
(I only skimmed through the RFC, but the API mentioned there
looks more like an abstract one.)

I like the term "partial reliability" :)

Thanks,
- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina     werner@almesberger.net /
/_http://www.almesberger.net/____________________________________________/

  reply	other threads:[~2004-08-12  0:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-02  2:51 net-AIO and real-time TCP (blue sky research) Werner Almesberger
2004-08-10 15:51 ` Suparna Bhattacharya
2004-08-11 23:18   ` Werner Almesberger
2004-08-11 23:44     ` Sridhar Samudrala
2004-08-12  0:40       ` Werner Almesberger [this message]
2004-08-12  6:06         ` Sridhar Samudrala
2004-08-12 18:11         ` John Heffner
2004-08-12 12:07     ` Suparna Bhattacharya

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=20040811214044.U28020@almesberger.net \
    --to=werner@almesberger.net \
    --cc=netdev@oss.sgi.com \
    --cc=sri@us.ibm.com \
    --cc=suparna@in.ibm.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).