From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
To: linux-sctp@vger.kernel.org
Subject: Re: 64k streams not supported
Date: Fri, 21 Aug 2020 20:10:20 +0000 [thread overview]
Message-ID: <B2A8B53A-9704-4C42-84C7-05CD9615FC28@lurchi.franken.de> (raw)
In-Reply-To: <bedd13a72afd427ca4dbbdfa61985533@AcuMS.aculab.com>
> On 21. Aug 2020, at 17:59, David Laight <David.Laight@ACULAB.COM> wrote:
>
> Isn't SCTP supposed to support 65536 data streams?
Since the number of streams is exchanged in the INIT and INIT-ACK chunks
and encoded in a uint16_t, the number is 65535, not 65536.
So an implementation should be able to use up to 65535 incoming and
outgoing streams.
Best regards
Michael
> If I try to enable that many I get 10.
> Not surprising since the number of streams gets stored in a u16.
>
> The whole code base may need changing to save the highest
> valid stream?
>
> Since I don't actually need that many I'm not writing the patch.
>
> David
>
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
> Registration No: 1397386 (Wales)
>
next prev parent reply other threads:[~2020-08-21 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 15:59 64k streams not supported David Laight
2020-08-21 16:50 ` Marcelo Ricardo Leitner
2020-08-21 20:10 ` Michael Tuexen [this message]
2020-08-21 21:03 ` David Laight
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=B2A8B53A-9704-4C42-84C7-05CD9615FC28@lurchi.franken.de \
--to=michael.tuexen@lurchi.franken.de \
--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 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).