From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] tests/gem_userptr_blits: Expanded userptr test cases
Date: Wed, 22 Jan 2014 11:38:08 +0000 [thread overview]
Message-ID: <52DFADA0.50107@linux.intel.com> (raw)
In-Reply-To: <20140122112119.GE28361@nuc-i3427.alporthouse.com>
On 01/22/2014 11:21 AM, Chris Wilson wrote:
> On Wed, Jan 22, 2014 at 10:41:38AM +0000, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> A set of userptr test cases to support the new feature.
>
> Oh, and another thing...
>
> I guess we will want some benchmarks for mmu_notifier scaling since
> tracking the performance implications seems important.
What would be a realistic benchmark? My first thoughts were something like:
for each [unsync, sync]
for each N [1, 10, 100, 1000]
create N userptr bos
benchmark for T seconds: malloc/realloc/free
benchmark for T seconds: mmap/unmap
???
Add this as tests/gem_userptr_benchmark ?
Tvrtko
next prev parent reply other threads:[~2014-01-22 11:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 10:41 [PATCH] tests/gem_userptr_blits: Expanded userptr test cases Tvrtko Ursulin
2014-01-22 11:19 ` Chris Wilson
2014-01-22 11:21 ` Chris Wilson
2014-01-22 11:38 ` Tvrtko Ursulin [this message]
2014-01-22 11:41 ` Tvrtko Ursulin
2014-01-22 11:50 ` Chris Wilson
-- strict thread matches above, loose matches on Subject: below --
2014-01-29 13:30 Tvrtko Ursulin
2014-01-29 14:56 ` Chris Wilson
2014-01-29 20:11 ` Daniel Vetter
2014-01-30 9:20 ` Tvrtko Ursulin
2014-01-30 9:31 ` Daniel Vetter
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=52DFADA0.50107@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
/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.