From: Martin KaFai Lau <kafai@fb.com>
To: <bpf@vger.kernel.org>
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>, <kernel-team@fb.com>,
<netdev@vger.kernel.org>
Subject: [PATCH bpf-next 0/5] bpf: Follow up on bpf __sk_buff->tstamp
Date: Wed, 9 Mar 2022 01:04:44 -0800 [thread overview]
Message-ID: <20220309090444.3710464-1-kafai@fb.com> (raw)
This set is a follow up on the bpf side based on discussion [0].
Patch 1 is to remove some skbuff macros that are used in bpf filter.c
Patch 2 and 3 are to simplify the bpf insn rewrite on __sk_buff->tstamp.
Patch 4 is to simplify the bpf uapi by modeling the __sk_buff->tstamp
and __sk_buff->tstamp_type (was delivery_time_type) the same as its kernel
counter part skb->tstamp and skb->mono_delivery_time.
Patch 5 is to adjust the bpf selftests due to changes in patch 4.
[0]: https://lore.kernel.org/bpf/419d994e-ff61-7c11-0ec7-11fefcb0186e@iogearbox.net/
Martin KaFai Lau (5):
bpf: net: Remove TC_AT_INGRESS_OFFSET and
SKB_MONO_DELIVERY_TIME_OFFSET macro
bpf: Simplify insn rewrite on BPF_READ __sk_buff->tstamp
bpf: Simplify insn rewrite on BPF_WRITE __sk_buff->tstamp
bpf: Remove BPF_SKB_DELIVERY_TIME_NONE and rename
s/delivery_time_/tstamp_/
bpf: selftests: Update tests after s/delivery_time/tstamp/ change in
bpf.h
include/linux/filter.h | 2 +-
include/linux/skbuff.h | 10 +-
include/uapi/linux/bpf.h | 40 +++---
net/core/filter.c | 133 ++++++++----------
tools/include/uapi/linux/bpf.h | 40 +++---
.../selftests/bpf/progs/test_tc_dtime.c | 38 ++---
6 files changed, 125 insertions(+), 138 deletions(-)
--
2.30.2
next reply other threads:[~2022-03-09 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 9:04 Martin KaFai Lau [this message]
2022-03-09 9:04 ` [PATCH bpf-next 1/5] bpf: net: Remove TC_AT_INGRESS_OFFSET and SKB_MONO_DELIVERY_TIME_OFFSET macro Martin KaFai Lau
2022-03-09 9:04 ` [PATCH bpf-next 2/5] bpf: Simplify insn rewrite on BPF_READ __sk_buff->tstamp Martin KaFai Lau
2022-03-09 9:05 ` [PATCH bpf-next 3/5] bpf: Simplify insn rewrite on BPF_WRITE __sk_buff->tstamp Martin KaFai Lau
2022-03-09 9:05 ` [PATCH bpf-next 4/5] bpf: Remove BPF_SKB_DELIVERY_TIME_NONE and rename s/delivery_time_/tstamp_/ Martin KaFai Lau
2022-03-09 9:05 ` [PATCH bpf-next 5/5] bpf: selftests: Update tests after s/delivery_time/tstamp/ change in bpf.h Martin KaFai Lau
2022-03-10 22:00 ` [PATCH bpf-next 0/5] bpf: Follow up on bpf __sk_buff->tstamp patchwork-bot+netdevbpf
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=20220309090444.3710464-1-kafai@fb.com \
--to=kafai@fb.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.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