From: Alexander Lobakin <alexandr.lobakin@intel.com>
To: Tonghao Zhang <xiangxia.m.yue@gmail.com>
Cc: Alexander Lobakin <alexandr.lobakin@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>, Eric Dumazet <edumazet@google.com>,
Antoine Tenart <atenart@kernel.org>, Wei Wang <weiwan@google.com>,
Arnd Bergmann <arnd@arndb.de>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net v5 0/3] fix bpf_redirect to ifb netdev
Date: Wed, 8 Dec 2021 16:41:45 +0100 [thread overview]
Message-ID: <20211208154145.647078-1-alexandr.lobakin@intel.com> (raw)
In-Reply-To: <20211208145459.9590-1-xiangxia.m.yue@gmail.com>
From: Tonghao Zhang <xiangxia.m.yue@gmail.com>
Date: Wed, 8 Dec 2021 22:54:56 +0800
> From: Tonghao Zhang <xiangxia.m.yue@gmail.com>
>
> This patchset try to fix bpf_redirect to ifb netdev.
> Prevent packets loopback and perfromance drop, add check
> in sch egress.
Please provide a changelog in the cover letter. With the links to
your previous versions ideally.
Otherwise it becomes difficult to understand what are the changes
between them.
>
> Tonghao Zhang (3):
> net: core: set skb useful vars in __bpf_tx_skb
> net: sched: add check tc_skip_classify in sch egress
> selftests: bpf: add bpf_redirect to ifb
>
> net/core/dev.c | 3 +
> net/core/filter.c | 12 ++-
> tools/testing/selftests/bpf/Makefile | 1 +
> .../bpf/progs/test_bpf_redirect_ifb.c | 13 ++++
> .../selftests/bpf/test_bpf_redirect_ifb.sh | 73 +++++++++++++++++++
> 5 files changed, 101 insertions(+), 1 deletion(-)
> create mode 100644 tools/testing/selftests/bpf/progs/test_bpf_redirect_ifb.c
> create mode 100755 tools/testing/selftests/bpf/test_bpf_redirect_ifb.sh
>
> --
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: Jakub Kicinski <kuba@kernel.org>
> Cc: Alexei Starovoitov <ast@kernel.org>
> Cc: Daniel Borkmann <daniel@iogearbox.net>
> Cc: Andrii Nakryiko <andrii@kernel.org>
> Cc: Martin KaFai Lau <kafai@fb.com>
> Cc: Song Liu <songliubraving@fb.com>
> Cc: Yonghong Song <yhs@fb.com>
> Cc: John Fastabend <john.fastabend@gmail.com>
> Cc: KP Singh <kpsingh@kernel.org>
> Cc: Eric Dumazet <edumazet@google.com>
> Cc: Antoine Tenart <atenart@kernel.org>
> Cc: Alexander Lobakin <alexandr.lobakin@intel.com>
> Cc: Wei Wang <weiwan@google.com>
> Cc: Arnd Bergmann <arnd@arndb.de>
> --
> 2.27.0
Al
next parent reply other threads:[~2021-12-08 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211208145459.9590-1-xiangxia.m.yue@gmail.com>
2021-12-08 15:41 ` Alexander Lobakin [this message]
2021-12-08 15:53 ` Tonghao Zhang
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=20211208154145.647078-1-alexandr.lobakin@intel.com \
--to=alexandr.lobakin@intel.com \
--cc=andrii@kernel.org \
--cc=arnd@arndb.de \
--cc=ast@kernel.org \
--cc=atenart@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=weiwan@google.com \
--cc=xiangxia.m.yue@gmail.com \
--cc=yhs@fb.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 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®