public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: David Miller <davem@davemloft.net>
Cc: hidave.darkstar@gmail.com, greg@kroah.com, peterz@infradead.org,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH 01/12] Use mutex instead of semaphore in driver core
Date: Tue, 1 Jan 2008 23:00:08 -0800	[thread overview]
Message-ID: <20080102070008.GA31343@suse.de> (raw)
In-Reply-To: <20080101.212501.00751091.davem@davemloft.net>

On Tue, Jan 01, 2008 at 09:25:01PM -0800, David Miller wrote:
> From: Greg KH <gregkh@suse.de>
> Date: Tue, 1 Jan 2008 21:18:28 -0800
> 
> > But is the usage of this semaphore in the class code really a problem?
> > Has it been seen to cause issues anywhere?  Does it show up on any
> > benchmarks as being something that really needs to be replaced?
> 
> It's a question of maintainability and simplicity also Greg.
> 
> I actually have no idea why you're making any sort of fuss about this.
> To me it's so clear cut that we should do that.

For most cases, yes, I agree with this, but due to the lockdep issues
that occur here, and the whole mess with the suspend path and locking
the device tree, that has been hashed out many times in the past, I am
interested in trying to see if there is any real reason why this is
absolutely necessary to convert.

If no one has noticed any issues in this area, I think the complexity
that will be involved in any such conversion will strongly outweigh any
simplicity that might be expected.

I'm very open to potential patches to do this, just don't ignore the
issues that others have run into in the past when attempting this.

thanks,

greg k-h

  reply	other threads:[~2008-01-02  6:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-29  1:01 [PATCH 01/12] Use mutex instead of semaphore in driver core Dave Young
2007-12-29  1:29 ` Peter Zijlstra
2007-12-29  1:36   ` Dave Young
2007-12-29  1:40     ` Dave Young
2007-12-29  1:42     ` Peter Zijlstra
2007-12-29  1:52       ` Dave Young
2007-12-29  1:57         ` Peter Zijlstra
2007-12-29  2:03           ` Dave Young
2007-12-29  2:36             ` Dave Young
2007-12-29  4:42               ` Greg KH
2007-12-29  5:06                 ` Dave Young
2007-12-29  7:07                   ` Dave Young
2007-12-29 17:07                     ` Greg KH
2008-01-02  0:54                       ` Dave Young
2008-01-02  5:18                         ` Greg KH
2008-01-02  5:25                           ` David Miller
2008-01-02  7:00                             ` Greg KH [this message]
2008-01-02  7:52                               ` David Miller
2008-01-02 12:39                               ` Jarek Poplawski
2008-01-02 13:12                                 ` Jarek Poplawski
2008-01-02 16:08                               ` Alan Stern
2008-01-03  1:00                                 ` Dave Young
2008-01-02  5:37                           ` Dave Young
2007-12-29 22:01                     ` Alan Stern
2007-12-30  6:42                       ` David Brownell
2007-12-30 12:13                         ` Peter Zijlstra
2008-01-08 16:54                         ` Jiri Kosina
2008-01-02  0:58                       ` Dave Young
2008-01-02 16:06                         ` Alan Stern
2008-01-05  9:30           ` Andrew Morton

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=20080102070008.GA31343@suse.de \
    --to=gregkh@suse.de \
    --cc=davem@davemloft.net \
    --cc=greg@kroah.com \
    --cc=hidave.darkstar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=peterz@infradead.org \
    /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