From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw133936-133938 [PATCH] [v3, 4/4] hash: add SVE support for bulk key lookup
Date: Tue, 07 Nov 2023 09:12:18 -0800 (PST) [thread overview]
Message-ID: <654a6ff2.050a0220.78dd8.9df3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/133936
_apply patch failure_
Submitter: Yoan Picchi <yoan.picchi@arm.com>
Date: Tuesday, November 07 2023 12:18:45
Applied on: CommitID:2bbad8f974e00552d106c27e1d157a31179ab5ec
Apply patch set 133936-133938 failed:
Checking patch .mailmap...
Hunk #1 succeeded at 487 (offset 2 lines).
Hunk #2 succeeded at 1609 (offset 6 lines).
Checking patch lib/hash/rte_cuckoo_hash.c...
error: while searching for:
while (prim_hitmask[i]) {
uint32_t hit_index =
__builtin_ctzl(prim_hitmask[i])
>> 1;
uint32_t key_idx =
__atomic_load_n(
&primary_bkt[i]->key_idx[hit_index],
error: patch failed: lib/hash/rte_cuckoo_hash.c:2119
error: while searching for:
positions[i] = key_idx - 1;
goto next_key;
}
prim_hitmask[i] &= ~(3ULL << (hit_index << 1));
}
while (sec_hitmask[i]) {
uint32_t hit_index =
__builtin_ctzl(sec_hitmask[i])
>> 1;
uint32_t key_idx =
__atomic_load_n(
&secondary_bkt[i]->key_idx[hit_index],
error: patch failed: lib/hash/rte_cuckoo_hash.c:2145
Applied patch .mailmap cleanly.
Applying patch lib/hash/rte_cuckoo_hash.c with 2 rejects...
Hunk #1 applied cleanly.
Hunk #2 applied cleanly.
Hunk #3 applied cleanly.
Hunk #4 applied cleanly.
Hunk #5 applied cleanly.
Hunk #6 applied cleanly.
Hunk #7 applied cleanly.
Hunk #8 applied cleanly.
Hunk #9 applied cleanly.
Hunk #10 applied cleanly.
Hunk #11 applied cleanly.
Rejected hunk #12.
Rejected hunk #13.
Hunk #14 applied cleanly.
hint: Use 'git am --show-current-patch' to see the failed patch
diff a/lib/hash/rte_cuckoo_hash.c b/lib/hash/rte_cuckoo_hash.c (rejected hunks)
@@ -2119,7 +2169,7 @@ __bulk_lookup_lf(const struct rte_hash *h, const void **keys,
while (prim_hitmask[i]) {
uint32_t hit_index =
__builtin_ctzl(prim_hitmask[i])
- >> 1;
+ >> hitmask_padding;
uint32_t key_idx =
__atomic_load_n(
&primary_bkt[i]->key_idx[hit_index],
@@ -2145,13 +2195,13 @@ __bulk_lookup_lf(const struct rte_hash *h, const void **keys,
positions[i] = key_idx - 1;
goto next_key;
}
- prim_hitmask[i] &= ~(3ULL << (hit_index << 1));
+ prim_hitmask[i] &= ~(1 << (hit_index << hitmask_padding));
}
while (sec_hitmask[i]) {
uint32_t hit_index =
__builtin_ctzl(sec_hitmask[i])
- >> 1;
+ >> hitmask_padding;
uint32_t key_idx =
__atomic_load_n(
&secondary_bkt[i]->key_idx[hit_index],
Checking patch lib/hash/rte_cuckoo_hash.c...
error: lib/hash/rte_cuckoo_hash.c: does not match index
hint: Use 'git am --show-current-patch' to see the failed patch
Checking patch lib/hash/rte_cuckoo_hash.c...
error: lib/hash/rte_cuckoo_hash.c: does not match index
Checking patch lib/hash/rte_cuckoo_hash.h...
Applied patch lib/hash/rte_cuckoo_hash.h cleanly.
hint: Use 'git am --show-current-patch' to see the failed patch
https://lab.dpdk.org/results/dashboard/patchsets/28268/
UNH-IOL DPDK Community Lab
reply other threads:[~2023-11-07 17:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=654a6ff2.050a0220.78dd8.9df3SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).