The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Matthias Kaehlcke <matthias.kaehlcke@gmail.com>
To: "Eddie C. Dost" <ecd@atecom.com>
Cc: Kyle Moffett <mrmacman_g4@mac.com>,
	chas@cmf.nrl.navy.mil, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] use spinlock instead of binary mutex in idt77252 driver
Date: Mon, 23 Apr 2007 09:57:22 +0200	[thread overview]
Message-ID: <20070423075722.GE10339@traven> (raw)
In-Reply-To: <20070423074019.GA14549@gannet>

hi,

El Mon, Apr 23, 2007 at 09:40:19AM +0200 Eddie C. Dost ha dit:

> as long as mutexes are not converted to nop when CONFIG_SMP is not
> defined (I don't know what current kernels do), this is of course
> correct. You need to verify the headerfiles for the above.

i just checked this, neither the mutex header nor implementation files
handle things different for CONFIG_SMP. 

thanks for your comments

> On Mon, Apr 23, 2007 at 09:40:26AM +0200, Matthias Kaehlcke wrote:
> > El Mon, Apr 23, 2007 at 09:16:08AM +0200 Eddie C. Dost ha dit:
> >  
> > > Please note that the semaphore is used to lock the idt77252 config
> > > tables among multiple users including atmsigd even on single processor
> > > machines. Does this work with mutexes?
> > 
> > afaik mutexes have the same behaviour as binary semaphores that are
> > used as mutexes (always locked and unlocked by the same
> > process/thread):
> > 
> > ".. the semaphore type can officially be considered to be on its way
> > out. New code should not use semaphores, and old code which uses
> > semaphores as mutexes should be converted over when an opportunity
> > presents itself."
> > 
> > http://lwn.net/Articles/167034/
> > 
> > please correct me if i'm wrong, i'm just doing my first steps with
> > linux kernel development

-- 
Matthias Kaehlcke
Linux Application Developer
Barcelona

             You must have a plan. If you don't have a plan,
               you'll become part of somebody else's plan
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-

  reply	other threads:[~2007-04-23  7:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-22 21:39 [PATCH] use spinlock instead of binary mutex in idt77252 driver Matthias Kaehlcke
2007-04-22 23:50 ` Kyle Moffett
2007-04-23  6:55   ` Matthias Kaehlcke
2007-04-23  7:16     ` Eddie C. Dost
2007-04-23  7:40       ` Matthias Kaehlcke
2007-04-23  7:40         ` Eddie C. Dost
2007-04-23  7:57           ` Matthias Kaehlcke [this message]
2007-04-23  8:02           ` Satyam Sharma
2007-04-23  8:17   ` Christoph Hellwig
2007-04-23  8:35     ` Matthias Kaehlcke
2007-04-22 23:52 ` Satyam Sharma

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=20070423075722.GE10339@traven \
    --to=matthias.kaehlcke@gmail.com \
    --cc=chas@cmf.nrl.navy.mil \
    --cc=ecd@atecom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.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