From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Konstantin Ananyev" <konstantin.v.ananyev@yandex.ru>, <dev@dpdk.org>
Cc: <stephen@networkplumber.org>,
"Konstantin Ananyev" <konstantin.ananyev@huawei.com>
Subject: RE: [PATCH 0/3] fix bpf load hangs with six IPv6 addresses
Date: Thu, 27 Jun 2024 14:41:18 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F564@smartserver.smartshare.dk> (raw)
In-Reply-To: <20240627115531.1440-1-konstantin.v.ananyev@yandex.ru>
> From: Konstantin Ananyev <konstantin.ananyev@huawei.com>
>
> Konstantin Ananyev (3):
> bfp: fix MOV instruction evaluation
> bfp: fix load hangs with six IPv6 addresses
> test/bpf: add extra test cases for bpf convert
>
> app/test/test_bpf.c | 6 +
> lib/bpf/bpf_validate.c | 314 ++++++++++++++++++++++++++++++++++-------
> 2 files changed, 266 insertions(+), 54 deletions(-)
>
> --
> 2.35.3
Series-acked-by: Morten Brørup <mb@smartsharesystems.com>
next prev parent reply other threads:[~2024-06-27 12:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 11:55 [PATCH 0/3] fix bpf load hangs with six IPv6 addresses Konstantin Ananyev
2024-06-27 11:55 ` [PATCH 1/3] bfp: fix MOV instruction evaluation Konstantin Ananyev
2024-06-27 11:55 ` [PATCH 2/3] bfp: fix load hangs with six IPv6 addresses Konstantin Ananyev
2024-06-27 15:13 ` Stephen Hemminger
2024-06-27 11:55 ` [PATCH 3/3] test/bpf: add extra test cases for bpf convert Konstantin Ananyev
2024-06-27 15:15 ` Stephen Hemminger
2024-06-27 12:41 ` Morten Brørup [this message]
2024-06-27 18:04 ` [PATCH v2 0/3] fix bpf load hangs with six IPv6 addresses Konstantin Ananyev
2024-06-27 18:04 ` [PATCH v2 1/3] bfp: fix MOV instruction evaluation Konstantin Ananyev
2024-06-27 18:04 ` [PATCH v2 2/3] bfp: fix load hangs with six IPv6 addresses Konstantin Ananyev
2024-06-27 18:04 ` [PATCH v2 3/3] test/bpf: add extra test cases for bpf convert Konstantin Ananyev
2024-07-04 15:10 ` [PATCH v2 0/3] fix bpf load hangs with six IPv6 addresses David Marchand
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=98CBD80474FA8B44BF855DF32C47DC35E9F564@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=stephen@networkplumber.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 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.