[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180803204011.GH5482@localhost.localdomain>
Date: Fri, 3 Aug 2018 17:40:11 -0300
From: Marcelo Ricardo Leitner <marcelo.leitner@...il.com>
To: Konstantin Khorenko <khorenko@...tuozzo.com>
Cc: oleg.babin@...il.com, netdev@...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 1/2] net/sctp: Make wrappers for accessing in/out
streams
On Fri, Aug 03, 2018 at 07:21:01PM +0300, Konstantin Khorenko wrote:
> This patch introduces wrappers for accessing in/out streams indirectly.
> This will enable to replace physically contiguous memory arrays
> of streams with flexible arrays (or maybe any other appropriate
> mechanism) which do memory allocation on a per-page basis.
>
> Signed-off-by: Oleg Babin <obabin@...tuozzo.com>
> Signed-off-by: Konstantin Khorenko <khorenko@...tuozzo.com>
>
> ---
> v2 changes:
> sctp_stream_in() users are updated to provide stream as an argument,
> sctp_stream_{in,out}_ptr() are now just sctp_stream_{in,out}().
> ---
...
>
> struct sctp_stream {
> - struct sctp_stream_out *out;
> - struct sctp_stream_in *in;
> + struct flex_array *out;
> + struct flex_array *in;
If this patch was meant to be a preparation, shouldn't this belong to
the next patch instead?
Marcelo
Powered by blists - more mailing lists