From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: ast@plumgrid.com, hannes@stressinduktion.org, tgraf@suug.ch,
viro@ZenIV.linux.org.uk, ebiederm@xmission.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/5] BPF updates
Date: Sun, 01 Nov 2015 12:16:51 -0500 (EST) [thread overview]
Message-ID: <20151101.121651.1361940420226820359.davem@davemloft.net> (raw)
In-Reply-To: <cover.1446126105.git.daniel@iogearbox.net>
From: Daniel Borkmann <daniel@iogearbox.net>
Date: Thu, 29 Oct 2015 14:58:05 +0100
> This set adds support for persistent maps/progs. Please see
> individual patches for further details. A man-page update
> to bpf(2) will be sent later on, also a iproute2 patch for
> support in tc.
>
> Thanks!
>
> v1 -> v2:
> - Reworked most of patch 4 and 5
> - Rebased to latest net-next
I'm going to let this sit for a little bit of review time since
this facility seems to be generating at least a little bit of
controversy :-)
next prev parent reply other threads:[~2015-11-01 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 13:58 Daniel Borkmann
2015-10-29 13:58 ` [PATCH net-next v2 1/5] bpf: abstract anon_inode_getfd invocations Daniel Borkmann
2015-10-29 13:58 ` [PATCH net-next v2 2/5] bpf: align and clean bpf_{map,prog}_get helpers Daniel Borkmann
2015-10-29 13:58 ` [PATCH net-next v2 3/5] bpf: consolidate bpf_prog_put{,_rcu} dismantle paths Daniel Borkmann
2015-10-29 13:58 ` [PATCH net-next v2 4/5] bpf: add support for persistent maps/progs Daniel Borkmann
2015-10-29 13:58 ` [PATCH net-next v2 5/5] bpf: add sample usages " Daniel Borkmann
2015-11-01 17:16 ` David Miller [this message]
2015-11-03 3:48 ` [PATCH net-next v2 0/5] BPF updates 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=20151101.121651.1361940420226820359.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=ebiederm@xmission.com \
--cc=hannes@stressinduktion.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
--cc=viro@ZenIV.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®