All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: linux-sctp@vger.kernel.org
Subject: Re: Clean up messages for a particular stream
Date: Tue, 30 Jun 2015 17:38:04 +0000	[thread overview]
Message-ID: <20150630173804.GA1943@localhost.localdomain> (raw)
In-Reply-To: <CAAyB5c+_yBxrer7tA5a69E+-0nsZRCqLV4+MVHEAP_Ppg49whg@mail.gmail.com>

Hi,

In-Reply-To: <CAAyB5c+_yBxrer7tA5a69E+-0nsZRCqLV4+MVHEAP_Ppg49whg@mail.gmail.com>

On Tue, Jun 30, 2015 at 09:56:50AM -0700, Jerry Jerry wrote:
>  Hello everyone,
> 
> We currently encounter an issue where we re-use the streams in a SCTP
> connection. However, data from different message contexts may co-exist
> in the send/recv buffers for that reused stream. I'm wondering if
> there is any special API that allow us to flush the data for just one
> particular stream in a SCTP connection just before we reuse it, or we
> have to do this from application?
> 
> I've been searching but were unable to find a good answer yet. Your
> advices would be greatly appreciated!

In short, no.. you have to do it in your application.

If you're using unordered delivery, I'm afraid that clean cut is just
not possible at all as there will always be the chance of a late packet
getting delivered. That is, unless you add a layer abstracting that,
like a substream id or something like that...

And if you're using ordered delivery, it would mean to close/re-open a
stream or a signaling for such event, but those operations don't exist.

  Marcelo

  parent reply	other threads:[~2015-06-30 17:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 16:56 Clean up messages for a particular stream Jerry Jerry
2015-06-30 17:18 ` Vlad Yasevich
2015-06-30 17:38 ` Marcelo Ricardo Leitner [this message]
2015-06-30 17:41 ` Marcelo Ricardo Leitner

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=20150630173804.GA1943@localhost.localdomain \
    --to=marcelo.leitner@gmail.com \
    --cc=linux-sctp@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.