From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org
Subject: [PATCH v1 0/4] fbarray lookahead/lookbehind fixes
Date: Mon, 8 Jul 2024 17:07:31 +0100 [thread overview]
Message-ID: <cover.1720454625.git.anatoly.burakov@intel.com> (raw)
Once upon a time, a few patches were submitted by Vipin P R:
https://patches.dpdk.org/project/dpdk/patch/1673615669-21011-2-git-send-email-vipinp@vmware.com/
https://patches.dpdk.org/project/dpdk/patch/1673615669-21011-3-git-send-email-vipinp@vmware.com/
https://patches.dpdk.org/project/dpdk/patch/1673615669-21011-2-git-send-email-vipinp@vmware.com/
https://patches.dpdk.org/project/dpdk/patch/1673615669-21011-3-git-send-email-vipinp@vmware.com/
They were reviewed and changes were requested, but the author never followed up
and these patches kind of fell through the cracks. The patches fixed real bugs
in fbarray lookahead/lookbehind behavior, so now these bugs have resurfaced in
some customer reports.
This is a resubmit with improvements and added unit tests.
Anatoly Burakov (4):
fbarray: fix incorrect lookahead behavior
fbarray: fix incorrect lookbehind behavior
fbarray: fix lookahead ignore mask handling
fbarray: fix lookbehind ignore mask handling
app/test/test_fbarray.c | 102 ++++++++++++++++++++++++++++
lib/eal/common/eal_common_fbarray.c | 28 ++++++--
2 files changed, 123 insertions(+), 7 deletions(-)
--
2.43.0
next reply other threads:[~2024-07-08 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 16:07 Anatoly Burakov [this message]
2024-07-08 16:07 ` [PATCH v1 1/4] fbarray: fix incorrect lookahead behavior Anatoly Burakov
2024-07-08 16:07 ` [PATCH v1 2/4] fbarray: fix incorrect lookbehind behavior Anatoly Burakov
2024-07-08 16:07 ` [PATCH v1 3/4] fbarray: fix lookahead ignore mask handling Anatoly Burakov
2024-07-08 16:07 ` [PATCH v1 4/4] fbarray: fix lookbehind " Anatoly Burakov
2024-07-09 4:57 ` [PATCH v1 0/4] fbarray lookahead/lookbehind fixes 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=cover.1720454625.git.anatoly.burakov@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.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.