public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Christoph Hellwig <hch@infradead.org>, Bill Huey <bhuey@lnxw.com>,
	Esben Nielsen <simlo@phys.au.dk>,
	Daniel Walker <dwalker@mvista.com>, Dave Chinner <dgc@sgi.com>,
	greg@kroah.com, Nathan Scott <nathans@sgi.com>,
	Steve Lord <lord@xfs.org>,
	linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: RT and XFS
Date: Tue, 19 Jul 2005 15:50:56 +0200	[thread overview]
Message-ID: <20050719135056.GA19552@elte.hu> (raw)
In-Reply-To: <20050719132750.GA20595@infradead.org>


* Christoph Hellwig <hch@infradead.org> wrote:

> On Tue, Jul 19, 2005 at 02:34:57PM +0200, Ingo Molnar wrote:
> > (I do disagree with Christoph on another point: i do think we eventually 
> > want to change the standard semaphore type in a similar fashion upstream 
> > as well - but that probably has to come with a s/struct semaphore/struct 
> > mutex/ change as well.)
> 
> Actually having a mutex_t in mainline would be a good idea even 
> without preempt rt, to document better what kind of locking we expect.

cool! I'll cook up a patch for that. Right now these are the numbers: 
there are 526 uses of struct semaphore in 2.6.12. In the -RT tree i had 
to change 23 of them to be compat_semaphore - i.e. 23 uses were 
definitely non-mutex.

(We sure have missed some cases - but it would be fair to say that the 
expected number of cases is less than 50, and that we've mapped the most 
common ones already. That makes it a 90%/10% splitup: more than 90% of 
all struct semaphore use is pure mutex.)

Of the remaining <10% cases, the majority is of the type of completions, 
and there are a handful of (<10) cases of 'counted semaphore' uses: 
semaphores with a count larger than 1. (e.g. ACPI uses it to count 
resources, some audio code too - but it's very rare) Btw., that's the 
only 'true' (in terms of CS) semaphore use.

	Ingo

  reply	other threads:[~2005-07-19 13:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12 23:01 RT and XFS Daniel Walker
2005-07-12 23:39 ` William Weston
2005-07-13  0:25 ` Nathan Scott
2005-07-13  0:41   ` Daniel Walker
2005-07-13  0:37     ` Nathan Scott
2005-07-13  6:47   ` Ingo Molnar
2005-07-13 16:45     ` Daniel Walker
2005-07-14  0:22       ` Nathan Scott
2005-07-14  3:50         ` Dave Chinner
2005-07-14  4:10           ` Daniel Walker
     [not found]             ` <20050714052347.GA18813@elte.hu>
2005-07-14 15:56               ` Daniel Walker
2005-07-14 16:08                 ` Christoph Hellwig
2005-07-18 12:10                   ` Esben Nielsen
2005-07-19  3:26                     ` Bill Huey
2005-07-19 12:34                       ` Ingo Molnar
2005-07-19 13:27                         ` Christoph Hellwig
2005-07-19 13:50                           ` Ingo Molnar [this message]
2005-07-14 16:08                 ` Christoph Hellwig
2005-07-15 10:23             ` Ingo Molnar
2005-07-15 16:16               ` Daniel Walker
2005-07-18 11:33                 ` Esben Nielsen
2005-07-19  3:31                 ` Bill Huey

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=20050719135056.GA19552@elte.hu \
    --to=mingo@elte.hu \
    --cc=bhuey@lnxw.com \
    --cc=dgc@sgi.com \
    --cc=dwalker@mvista.com \
    --cc=greg@kroah.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=lord@xfs.org \
    --cc=nathans@sgi.com \
    --cc=simlo@phys.au.dk \
    /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