Linux Test Project
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: Wei Gao <wegao@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] memcontrol: Add bind_to_current_cpu() helper
Date: Wed, 30 Sep 2026 08:11:14 +0000	[thread overview]
Message-ID: <20260930081114.8885-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260930035332.3360-2-wegao@suse.com>

Hi Wei,

On Wed Sep 30 03:53:14 2026 +0000, Wei Gao via ltp wrote:
> memcontrol: Add bind_to_current_cpu() helper

--- [PATCH 1/2] ---

> Add bind_to_current_cpu() to memcontrol_common.h to allow memcg tests
> to bind the test process to a single CPU.

The commit message only restates what changed. Explain why memcg tests
need to bind to a single CPU (e.g. to prevent multi-CPU per-CPU memcg stock
charge accumulation from causing reclaim variance in hierarchical tests).

> +static inline void bind_to_current_cpu(void)
> +{
> +	int cpu = sched_getcpu();
> +	size_t mask_size;
> +	cpu_set_t *mask;

Include <sched.h> in memcontrol_common.h. The function uses sched_getcpu(),
cpu_set_t, CPU_ALLOC(), and sched_setaffinity(), but currently relies on
indirect inclusion via tst_test.h.

Verdict - Needs revision

Pre-existing issues:
- memcontrol03.c:209: sleep(1) is used in a polling loop. Polling loops
  should use exponential backoff or checkpoint synchronization.
- memcontrol03.c:241, memcontrol04.c:240: fd validity is checked with
  fd > -1 instead of the LTP convention fd != -1.

---
Note:

The agent can sometimes produce false positives although often its
findings are genuine. If you find issues with the review, please
comment this email or ignore the suggestions.

Regards,
LTP AI Reviewer

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-09-30  8:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29  2:23 [LTP] [PATCH v1] memcontrol03: Bind to single CPU on systems with 64KB pagesize Wei Gao via ltp
2026-09-29  4:35 ` [LTP] " linuxtestproject.agent
2026-09-29 17:01 ` [LTP] [PATCH v1] " Michal Koutný via ltp
2026-09-30  3:53 ` [LTP] [PATCH v2 0/2] memcontrol03, memcontrol04: Bind test process to a single CPU Wei Gao via ltp
2026-09-30  3:53   ` [LTP] [PATCH v2 1/2] memcontrol: Add bind_to_current_cpu() helper Wei Gao via ltp
2026-09-30  8:11     ` linuxtestproject.agent [this message]
2026-09-30 11:25       ` [LTP] " Wei Gao via ltp
2026-09-30  3:53   ` [LTP] [PATCH v2 2/2] memcontrol03, memcontrol04: Bind test process to a single CPU Wei Gao via ltp
     [not found] ` <20260929-second-foyer-87225078267f@there>
2026-09-30  3:55   ` [LTP] [PATCH v1] memcontrol03: Bind to single CPU on systems with 64KB pagesize Wei Gao via ltp

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=20260930081114.8885-1-linuxtestproject.agent@gmail.com \
    --to=linuxtestproject.agent@gmail.com \
    --cc=ltp@lists.linux.it \
    --cc=wegao@suse.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