From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: john.fastabend@gmail.com, ast@fb.com, netdev@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH net-next 0/2] Two BPF smap related followups
Date: Thu, 17 Aug 2017 17:22:35 +0200 [thread overview]
Message-ID: <cover.1502983087.git.daniel@iogearbox.net> (raw)
Fixing preemption imbalance and consolidating prologue
generation. Thanks!
Daniel Borkmann (2):
bpf: don't enable preemption twice in smap_do_verdict
bpf: reuse tc bpf prologue for sk skb progs
kernel/bpf/sockmap.c | 3 ++-
net/core/filter.c | 47 ++++++++++-------------------------------------
2 files changed, 12 insertions(+), 38 deletions(-)
--
1.9.3
next reply other threads:[~2017-08-17 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 15:22 Daniel Borkmann [this message]
2017-08-17 15:22 ` [PATCH net-next 1/2] bpf: don't enable preemption twice in smap_do_verdict Daniel Borkmann
2017-08-17 16:03 ` John Fastabend
2017-08-17 16:10 ` Alexei Starovoitov
2017-08-17 15:22 ` [PATCH net-next 2/2] bpf: reuse tc bpf prologue for sk skb progs Daniel Borkmann
2017-08-17 16:05 ` John Fastabend
2017-08-17 16:12 ` Alexei Starovoitov
2017-08-17 17:25 ` [PATCH net-next 0/2] Two BPF smap related followups 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=cover.1502983087.git.daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@fb.com \
--cc=davem@davemloft.net \
--cc=john.fastabend@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).