From: Ashutosh Dixit <ashutosh.dixit@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH] Add a light version of gem_exec_create@forked
Date: Tue, 05 Mar 2019 20:32:58 -0800 [thread overview]
Message-ID: <87lg1s62rp.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <155177532783.27405.12198294774516832319@skylake-alporthouse-com>
On Tue, 05 Mar 2019 00:42:07 -0800,
Chris Wilson wrote:
>
> Quoting Swathi Dhanavanthri (2019-03-05 01:16:55)
> > igt@gem-exec-create@forked runs a single uniterrupted loop for as long
> > as the timeout specified ie 150s. Reducing this to 15s.
>
> There is a light version already. The real question is this heavy
> enough? What more can we do to induce fault handling along these paths
> in the kernel? Run a pagecache hog in the background? Use
> faultinjection?
From these comments (and also from a limited understanding of the source
code for the test due to the deferred free's) it appeared that this test is
being run for so long so that it can exhaust system memory. But we just ran
the test with 'top' on and we don't see the system memory go down at
all. If that is indeed the case then what is the point of running this test
for so long? Thanks!
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-03-06 4:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 1:16 [igt-dev] [PATCH] Add a light version of gem_exec_create@forked Swathi Dhanavanthri
2019-03-05 2:25 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-03-05 8:03 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-03-05 8:42 ` [igt-dev] [PATCH] " Chris Wilson
2019-03-06 4:32 ` Ashutosh Dixit [this message]
2019-03-06 9:01 ` Chris Wilson
2019-03-05 8:45 ` Chris Wilson
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=87lg1s62rp.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.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