From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] tests/gem_userptr_benchmark: Benchmarking userptr surfaces and impact
Date: Thu, 06 Feb 2014 10:20:58 +0000 [thread overview]
Message-ID: <52F3620A.4030903@linux.intel.com> (raw)
In-Reply-To: <20140205175144.GK17001@phenom.ffwll.local>
On 02/05/2014 05:51 PM, Daniel Vetter wrote:
> On Wed, Feb 05, 2014 at 05:33:06PM +0000, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> This adds a small benchmark for the new userptr functionality.
>>
>> Apart from basic surface creation and destruction, also tested is the
>> impact of having userptr surfaces in the process address space. Reason
>> for that is the impact of MMU notifiers on common address space
>> operations like munmap() which is per process.
>>
>> v2:
>> * Moved to benchmarks.
>
> I'd just keep it as an igt testcase, beating on the kernel a bit can't
> hurt. And we have piles of other benchmark-like testcase already around.
Are you sure? Ben suggested to move it there and I actually agree it
makes more sense since it is mostly testing indirect effects on
(seemingly) unrelated operations. Not to mention benchmark directory
already exists and it is rather empty compared to tests...
Tvrtko
prev parent reply other threads:[~2014-02-06 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 12:41 [RFC][PATCH] Userptr benchmark Tvrtko Ursulin
2014-02-05 12:41 ` [PATCH] tests/gem_userptr_benchmark: Benchmarking userptr surfaces and impact Tvrtko Ursulin
2014-02-05 14:25 ` [RFC][PATCH] Userptr benchmark Chris Wilson
2014-02-05 17:33 ` [PATCH] tests/gem_userptr_benchmark: Benchmarking userptr surfaces and impact Tvrtko Ursulin
2014-02-05 17:51 ` Daniel Vetter
2014-02-06 10:20 ` Tvrtko Ursulin [this message]
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=52F3620A.4030903@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=daniel@ffwll.ch \
/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