Thread (32 messages) 32 messages, 6 authors, 2018-08-11

Re: [PATCH v2 0/2] net/sctp: Avoid allocating high order memory with kmalloc()

From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Date: 2018-08-08 17:08:57
Also in: linux-sctp

On Mon, Aug 06, 2018 at 09:34:05AM +0000, David Laight wrote:
From: Michael Tuexen
quoted
Sent: 03 August 2018 21:57
...
quoted
quoted
quoted
Given how useless SCTP streams are, does anything actually use
more than about 4?
Maybe Michael can help us with that. I'm also curious now.
In the context of SIGTRAN I have seen 17 streams...
Ok, I've seen 17 there as well, 5 is probably more common.
quoted
In the context of WebRTC I have seen more streams. In general,
the streams concept seems to be useful. QUIC has lots of streams.
That means the migration to flex_array should not have a noticeable
impact, as for a small number of streams it will behave just as the
same as it does now. (yes, considering the app won't use high-order
stream id's just because)

...
Thought....
Could we let the application set large stream-ids, but actually mask them
down to (say) 32 for the protocol code?
This would require both peers to know about the mapping, as stream ids
must be same on both sides. Seems to be it is better to just adjust
the application and make use of low numbers.

  Marcelo
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help