From: Suchit Karunakaran <suchitkarunakaran@gmail.com>
To: andrii@kernel.org, eddyz87@gmail.com, ast@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, memxor@gmail.com,
song@kernel.org, yonghong.song@linux.dev, shuah@kernel.org,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Suchit Karunakaran <suchitkarunakaran@gmail.com>
Subject: [PATCH] bpf: replace pop/push emptiness check with bpf_list_empty()
Date: Sun, 24 May 2026 00:04:22 +0530 [thread overview]
Message-ID: <20260523183422.124105-1-suchitkarunakaran@gmail.com> (raw)
Simplify fq_flows_is_empty() by replacing the pop/push based emptiness
check with a direct call to bpf_list_empty().
This avoids unnecessary list mutation and simplifies the code while
preserving correctness.
Signed-off-by: Suchit Karunakaran <suchitkarunakaran@gmail.com>
---
tools/testing/selftests/bpf/progs/bpf_qdisc_fq.c | 10 +++-------
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git a/tools/testing/selftests/bpf/progs/bpf_qdisc_fq.c b/tools/testing/selftests/bpf/progs/bpf_qdisc_fq.c
index 1a3233a275c7..3b05ac1d7c77 100644
--- a/tools/testing/selftests/bpf/progs/bpf_qdisc_fq.c
+++ b/tools/testing/selftests/bpf/progs/bpf_qdisc_fq.c
@@ -197,17 +197,13 @@ static bool
fq_flows_is_empty(struct bpf_list_head *head, struct bpf_spin_lock *lock)
{
struct bpf_list_node *node;
+ bool empty;
bpf_spin_lock(lock);
- node = bpf_list_pop_front(head);
- if (node) {
- bpf_list_push_front(head, node);
- bpf_spin_unlock(lock);
- return false;
- }
+ empty = bpf_list_empty(head);
bpf_spin_unlock(lock);
- return true;
+ return empty;
}
/* flow->age is used to denote the state of the flow (not-detached, detached, throttled)
--
2.54.0
next reply other threads:[~2026-05-23 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 18:34 Suchit Karunakaran [this message]
2026-05-23 19:20 ` [PATCH] bpf: replace pop/push emptiness check with bpf_list_empty() bot+bpf-ci
2026-05-25 18:08 ` Emil Tsalapatis
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=20260523183422.124105-1-suchitkarunakaran@gmail.com \
--to=suchitkarunakaran@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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