From: Jonathan Lemon <jonathan.lemon@gmail.com>
To: <bjorn.topel@intel.com>, <magnus.karlsson@intel.com>,
<toke@redhat.com>, <brouer@redhat.com>, <daniel@iogearbox.net>,
<ast@kernel.org>
Cc: <kernel-team@fb.com>, <netdev@vger.kernel.org>
Subject: [PATCH v5 bpf-next 2/4] bpf/tools: sync bpf.h
Date: Thu, 6 Jun 2019 13:59:41 -0700 [thread overview]
Message-ID: <20190606205943.818795-3-jonathan.lemon@gmail.com> (raw)
In-Reply-To: <20190606205943.818795-1-jonathan.lemon@gmail.com>
Sync uapi/linux/bpf.h
Signed-off-by: Jonathan Lemon <jonathan.lemon@gmail.com>
---
tools/include/uapi/linux/bpf.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/tools/include/uapi/linux/bpf.h b/tools/include/uapi/linux/bpf.h
index 7c6aef253173..ae0907d8c03a 100644
--- a/tools/include/uapi/linux/bpf.h
+++ b/tools/include/uapi/linux/bpf.h
@@ -3083,6 +3083,10 @@ struct bpf_sock_tuple {
};
};
+struct bpf_xdp_sock {
+ __u32 queue_id;
+};
+
#define XDP_PACKET_HEADROOM 256
/* User return codes for XDP prog type.
--
2.17.1
next prev parent reply other threads:[~2019-06-06 20:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 20:59 [PATCH v5 bpf-next 0/4] Better handling of xskmap entries Jonathan Lemon
2019-06-06 20:59 ` [PATCH v5 bpf-next 1/4] bpf: Allow bpf_map_lookup_elem() on an xskmap Jonathan Lemon
2019-06-06 20:59 ` Jonathan Lemon [this message]
2019-06-07 6:17 ` [PATCH v5 bpf-next 2/4] bpf/tools: sync bpf.h Martin Lau
2019-06-06 20:59 ` [PATCH v5 3/4] tools/bpf: Add bpf_map_lookup_elem selftest for xskmap Jonathan Lemon
2019-06-07 6:18 ` Martin Lau
2019-06-06 20:59 ` [PATCH v5 4/4] libbpf: remove qidconf and better support external bpf programs Jonathan Lemon
2019-06-09 6:52 ` [PATCH v5 bpf-next 0/4] Better handling of xskmap entries Björn Töpel
2019-06-11 6:36 ` Alexei Starovoitov
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=20190606205943.818795-3-jonathan.lemon@gmail.com \
--to=jonathan.lemon@gmail.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@intel.com \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=toke@redhat.com \
/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.