[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170411.143916.598983200463509517.davem@davemloft.net>
Date: Tue, 11 Apr 2017 14:39:16 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: johannes@...solutions.net
Cc: netdev@...r.kernel.org, alexei.starovoitov@...il.com,
daniel@...earbox.net, johannes.berg@...el.com
Subject: Re: [PATCH net-next v4 2/2] bpf: remove struct bpf_map_type_list
From: Johannes Berg <johannes@...solutions.net>
Date: Tue, 11 Apr 2017 15:34:58 +0200
> From: Johannes Berg <johannes.berg@...el.com>
>
> There's no need to have struct bpf_map_type_list since
> it just contains a list_head, the type, and the ops
> pointer. Since the types are densely packed and not
> actually dynamically registered, it's much easier and
> smaller to have an array of type->ops pointer. Also
> initialize this array statically to remove code needed
> to initialize it.
>
> In order to save duplicating the list, move it to the
> types header file added by the previous patch and
> include it in the same fashion.
>
> Signed-off-by: Johannes Berg <johannes.berg@...el.com>
Applied.
Powered by blists - more mailing lists