All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: johannes@sipsolutions.net
Cc: netdev@vger.kernel.org, alexei.starovoitov@gmail.com,
	daniel@iogearbox.net, johannes.berg@intel.com
Subject: Re: [PATCH net-next v4 2/2] bpf: remove struct bpf_map_type_list
Date: Tue, 11 Apr 2017 14:39:16 -0400 (EDT)	[thread overview]
Message-ID: <20170411.143916.598983200463509517.davem@davemloft.net> (raw)
In-Reply-To: <20170411133458.26816-2-johannes@sipsolutions.net>

From: Johannes Berg <johannes@sipsolutions.net>
Date: Tue, 11 Apr 2017 15:34:58 +0200

> From: Johannes Berg <johannes.berg@intel.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@intel.com>

Applied.

  parent reply	other threads:[~2017-04-11 18:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11 13:34 [PATCH net-next v4 1/2] bpf: remove struct bpf_prog_type_list Johannes Berg
2017-04-11 13:34 ` [PATCH net-next v4 2/2] bpf: remove struct bpf_map_type_list Johannes Berg
2017-04-11 14:43   ` Alexei Starovoitov
2017-04-11 14:48     ` Daniel Borkmann
2017-04-11 18:39   ` David Miller [this message]
2017-04-11 14:41 ` [PATCH net-next v4 1/2] bpf: remove struct bpf_prog_type_list Alexei Starovoitov
2017-04-11 18:39 ` David Miller

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=20170411.143916.598983200463509517.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alexei.starovoitov@gmail.com \
    --cc=daniel@iogearbox.net \
    --cc=johannes.berg@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.