[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cd32848f0018432fad7246620d32c4e5@AcuMS.aculab.com>
Date: Fri, 3 Aug 2018 16:43:28 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Konstantin Khorenko' <khorenko@...tuozzo.com>,
Marcelo Ricardo Leitner <marcelo.leitner@...il.com>
CC: "oleg.babin@...il.com" <oleg.babin@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-sctp@...r.kernel.org" <linux-sctp@...r.kernel.org>,
"David S . Miller" <davem@...emloft.net>,
"Vlad Yasevich" <vyasevich@...il.com>,
Neil Horman <nhorman@...driver.com>,
"Xin Long" <lucien.xin@...il.com>,
Andrey Ryabinin <aryabinin@...tuozzo.com>
Subject: RE: [PATCH v2 0/2] net/sctp: Avoid allocating high order memory with
kmalloc()
From: Konstantin Khorenko
> Sent: 03 August 2018 17:21
>
> Each SCTP association can have up to 65535 input and output streams.
> For each stream type an array of sctp_stream_in or sctp_stream_out
> structures is allocated using kmalloc_array() function. This function
> allocates physically contiguous memory regions, so this can lead
> to allocation of memory regions of very high order, i.e.:
...
Given how useless SCTP streams are, does anything actually use
more than about 4?
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists