From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Thomas Hellstrom <thellstrom@vmware.com>,
Daniel Vetter <daniel@ffwll.ch>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: ww-mutex performance tests?
Date: Tue, 3 Apr 2018 10:37:16 +0200 [thread overview]
Message-ID: <2baa9638-74bb-5532-69f0-84bc8b0ae849@linux.intel.com> (raw)
In-Reply-To: <f3a93785-40ac-1abf-3ecd-a85a130465fa@vmware.com>
Op 02-04-18 om 19:49 schreef Thomas Hellstrom:
> Maarten, Daniel,
>
> Do we have any ww-mutex performance tests somewhere that can be used to test the impact of implementation details on various locking scenarios?
>
> Thanks,
>
> /Thomas
>
>
The thing that comes to my mind are some of the kms_cursor_legacy tests that have been proven to be sensitive to locking issues before.
All subtests with (pipe-*/all-pipes)-(single/forked/torture)-(bo/move) try to do cursor updates as fast as possible, and report how many updates have been done.
~Maarten
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-04-03 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 17:49 ww-mutex performance tests? Thomas Hellstrom
2018-04-03 8:37 ` Maarten Lankhorst [this message]
2018-04-04 17:12 ` Thomas Hellstrom
2018-04-04 18:02 ` Daniel Vetter
2018-04-05 6:41 ` Christian König
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=2baa9638-74bb-5532-69f0-84bc8b0ae849@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=thellstrom@vmware.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