From: David Laight <David.Laight@ACULAB.COM>
To: linux-sctp@vger.kernel.org
Subject: RE: [PATCH net] sctp: Free connecting association if there is a pending signal
Date: Wed, 11 Jul 2018 11:09:33 +0000 [thread overview]
Message-ID: <e4aa0b572a40416eb9622d0a119a489b@AcuMS.aculab.com> (raw)
In-Reply-To: <20180709101142.GA1820@bordel.klfree.net>
From: Petr Malat
> Sent: 11 July 2018 10:13
...
> I can look further and try to change the patch to free the association
> only for blocking sockets, but that leads me to a question what is
> actually the intended behavior for these cases, should SCTP be as close
> to TCP as possible (to make s/IPPROTO_TCP/IPPROTO_SCTP/ working for
> most applications)?
Most TCP applications will fail to work properly over SCTP for
other reasons.
At least one problem is that unless the application enables receipt
of 'sctp_association_event' it won't be told about connection
restarts and will get very confused by the missing data.
It is also worth noting that TCP is likely to be considerably
faster than SCTP.
Partially because the SCTP code is significantly more complicated,
and partially because it is difficult for an application to get
multiple data chunks into a single ethernet frame (unless the
traffic pattern allows Nagle be enabled).
Even some of the protocols which (I think) were co-developed with
SCTP (I'm thinking about SIGTRAN M3UA and M2PA) have mis-understandings
about the way SCTP behaves and probably work better over TCP!
David
next prev parent reply other threads:[~2018-07-11 11:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 10:11 [PATCH net] sctp: Free connecting association if there is a pending signal Petr Malat
2018-07-09 12:15 ` Neil Horman
2018-07-09 15:37 ` Petr Malat
2018-07-09 19:08 ` Neil Horman
2018-07-11 9:12 ` Petr Malat
2018-07-11 10:43 ` Neil Horman
2018-07-11 11:09 ` David Laight [this message]
2018-07-11 17:20 ` Petr Malat
2018-07-11 23:43 ` Neil Horman
2018-07-12 10:27 ` Petr Malat
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=e4aa0b572a40416eb9622d0a119a489b@AcuMS.aculab.com \
--to=david.laight@aculab.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.