From: Andi Shyti <andi.shyti@linux.intel.com>
To: Peter Senna Tschudin <me@petersenna.com>
Cc: igt-dev@lists.freedesktop.org, kamil.konieczny@linux.intel.com,
andi.shyti@linux.intel.com
Subject: Re: [PATCH] [PATCH i-g-t] tests/intel/gem_exec_capture: Reduce test size
Date: Tue, 9 Apr 2024 15:02:05 +0200 [thread overview]
Message-ID: <ZhU8TXtNsfE5srRp@ashyti-mobl2.lan> (raw)
In-Reply-To: <20240330145939.85030-1-me@petersenna.com>
Hi Peter,
On Sat, Mar 30, 2024 at 03:59:34PM +0100, Peter Senna Tschudin wrote:
> Before this patch, when using a chromebook-level CPU such as the N3150,
> with 8GB of RAM, the test `gem_exec_capture --run-subtest
> many-4K-incremental` could take 4 minutes to complete, and the
> `gem_exec_capture --run-subtest many-4K-zero` could take a minute.
>
> This patch reduces the test size by half, reducing the time to run by
> half as well.
>
> Signed-off-by: Peter Senna Tschudin <me@petersenna.com>
Acked-by: Andi Shyti <andi.shyti@linux.intel.com>
Andi
> ---
>
> This patch is only "testable" after my other patch that fixes the test,
> in the first place. As I write this, the other patch is here:
>
> https://patchwork.freedesktop.org/series/131602/
>
> tests/intel/gem_exec_capture.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/intel/gem_exec_capture.c b/tests/intel/gem_exec_capture.c
> index 2afb84283..3f454b897 100644
> --- a/tests/intel/gem_exec_capture.c
> +++ b/tests/intel/gem_exec_capture.c
> @@ -700,7 +700,7 @@ static void many(int fd, int dir, uint64_t size, unsigned int flags)
> igt_debug("Available objects in GTT:%"PRIu64", RAM:%"PRIu64"\n",
> gtt, ram);
>
> - count = min(gtt, ram) / 4;
> + count = min(gtt, ram) / 8;
> igt_require(count > 1);
>
> igt_require_memory(count, size, CHECK_RAM);
> --
> 2.44.0
next prev parent reply other threads:[~2024-04-09 13:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 14:59 [PATCH] [PATCH i-g-t] tests/intel/gem_exec_capture: Reduce test size Peter Senna Tschudin
2024-03-30 15:34 ` ✗ GitLab.Pipeline: warning for " Patchwork
2024-03-30 16:03 ` ✓ Fi.CI.BAT: success " Patchwork
2024-03-30 16:03 ` ✗ CI.xeBAT: failure " Patchwork
2024-03-31 4:27 ` ✗ Fi.CI.IGT: " Patchwork
2024-04-09 13:02 ` Andi Shyti [this message]
2024-06-05 15:16 ` [PATCH] [PATCH i-g-t] " Kamil Konieczny
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=ZhU8TXtNsfE5srRp@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=me@petersenna.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