mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sven-Thorsten Dietrich <sven@mvista.com>
To: david singleton <dsingleton@mvista.com>
Cc: robustmutexes@lists.osdl.org,
	Roy Reichwein <rreichwein@mvista.com>,
	linux-kernel@vger.kernel.org, Kevin Morgan <kmorgan@mvista.com>
Subject: Re: Robust Futexes status
Date: Sun, 23 Oct 2005 20:48:00 -0700	[thread overview]
Message-ID: <1130125681.5296.5.camel@imap.mvista.com> (raw)
In-Reply-To: <DFD605A2-4406-11DA-8ABF-000A959BB91E@mvista.com>

On Sun, 2005-10-23 at 13:52 -0700, david singleton wrote:
> 	Inaky Perez-Gonzalez   has a wonderful suite of performance, stress and
> functionality tests for the fusyn pthreads mutex package.

> 	The graphs are just to show relative performance for the different 
> flavor kernels.  The
> kernel's perform quite closely regardless of the 'flavor' of kernel.  
> The kernels have quite a few
> debugging options turned so I can look for any problems so performance 
> is not optimal.
> 

The Mutex ownership change seems to climb with waiting threads.

Its hard to tell with the log-n X-axis scale, but does this possibly
correlate to the deadlock-detect option?

If Deadlock-detect is enabled we should be seeing a graph proportional
to n-squared on a linear X axis.

If deadlock detect is disabled, the wait time should plateau for very
large N.

Sven


> 	It appears the robust futex functionality is healthy in all flavors of 
> kernel.
> 
> 	
> 
> David
> 
> 
> 
> 
-- 
***********************************
Sven-Thorsten Dietrich
Real-Time Software Architect
MontaVista Software, Inc.
1237 East Arques Ave.
Sunnyvale, CA 94085

Phone: 408.992.4515
Fax: 408.328.9204

http://www.mvista.com
Platform To Innovate
*********************************** 


  reply	other threads:[~2005-10-24  3:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-23 20:52 david singleton
2005-10-24  3:48 ` Sven-Thorsten Dietrich [this message]
2005-10-24 17:02   ` david singleton

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=1130125681.5296.5.camel@imap.mvista.com \
    --to=sven@mvista.com \
    --cc=dsingleton@mvista.com \
    --cc=kmorgan@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robustmutexes@lists.osdl.org \
    --cc=rreichwein@mvista.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

all inboxes | Powered by JetHome®