From: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
To: Arvind Yadav <arvind.yadav@intel.com>, <igt-dev@lists.freedesktop.org>
Cc: <nishit.sharma@intel.com>, <pravalika.gurram@intel.com>,
<kamil.konieczny@linux.intel.com>
Subject: Re: [i-g-t v2] tests/intel/xe_madvise: Skip purge tests under low RAM
Date: Fri, 12 Jun 2026 11:13:55 +0200 [thread overview]
Message-ID: <DJ6YFAG2CJJ7.1MSFMPH8P7TSM@intel.com> (raw)
In-Reply-To: <20260612045035.1942635-1-arvind.yadav@intel.com>
Hi Arvind,
On Fri Jun 12, 2026 at 6:50 AM CEST, Arvind Yadav wrote:
> The purge tests create memory pressure to trigger BO eviction. If the
> system is already low on RAM, this extra pressure can push the machine
> into OOM and kill the test before it can clean up.
>
> Check available RAM before starting the pressure allocation and skip when
> there is not enough memory.
>
> v2:
> - Drop unrelated chunk/max_t() changes. (Kamil)
> - Keep the original overpressure calculation. (Kamil)
>
> Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> Cc: Pravalika Gurram <pravalika.gurram@intel.com>
> Cc: Nishit Sharma <nishit.sharma@intel.com>
> Signed-off-by: Arvind Yadav <arvind.yadav@intel.com>
> ---
Reviewed-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
--
Best regards,
Sebastian
next prev parent reply other threads:[~2026-06-12 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 4:50 [i-g-t v2] tests/intel/xe_madvise: Skip purge tests under low RAM Arvind Yadav
2026-06-12 6:52 ` ✓ Xe.CI.BAT: success for tests/intel/xe_madvise: Skip purge tests under low RAM (rev2) Patchwork
2026-06-12 6:55 ` ✓ i915.CI.BAT: " Patchwork
2026-06-12 9:04 ` [i-g-t v2] tests/intel/xe_madvise: Skip purge tests under low RAM Sokolowski, Jan
2026-06-12 9:13 ` Sebastian Brzezinka [this message]
2026-06-12 22:53 ` ✓ Xe.CI.FULL: success for tests/intel/xe_madvise: Skip purge tests under low RAM (rev2) Patchwork
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=DJ6YFAG2CJJ7.1MSFMPH8P7TSM@intel.com \
--to=sebastian.brzezinka@intel.com \
--cc=arvind.yadav@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=nishit.sharma@intel.com \
--cc=pravalika.gurram@intel.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 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.