mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dave Young" <hidave.darkstar@gmail.com>
To: "Greg KH" <gregkh@suse.de>
Cc: "Greg KH" <greg@kroah.com>,
	"Peter Zijlstra" <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: Wed, 2 Jan 2008 13:37:52 +0800	[thread overview]
Message-ID: <a8e1da0801012137n78a18654t2a9d40225f0e8e1a@mail.gmail.com> (raw)
In-Reply-To: <20080102051828.GA24431@suse.de>

On Jan 2, 2008 1:18 PM, Greg KH <gregkh@suse.de> wrote:
> On Wed, Jan 02, 2008 at 08:54:53AM +0800, Dave Young wrote:
> > On Dec 30, 2007 1:07 AM, Greg KH <greg@kroah.com> wrote:
> > >
> > > On Sat, Dec 29, 2007 at 03:07:30PM +0800, Dave Young wrote:
> > > > On Dec 29, 2007 1:06 PM, Dave Young <hidave.darkstar@gmail.com> wrote:
> > > > >
> > > > > On Dec 29, 2007 12:42 PM, Greg KH <gregkh@suse.de> wrote:
> > > > > > On Sat, Dec 29, 2007 at 10:36:49AM +0800, Dave Young wrote:
> > > > > > > >
> > > > > > > The full boot dmesg with lockdep output is out, there's one warnings in it :
> > > > > >
> > > > > > Please fix that warning before the next repost of these patches (along
> > > > > > with fixing the problem of them not being able to be applied and
> > > > > > successfully built at every point in the series...)
> > > > > >
> > > > >
> > > > > Ok, thanks, I will fix them and repost.
> > > > >
> > > >
> > > > Hi,
> > > > After digging the code, I feel hard to fix the lockdep warning due to
> > > > some misterious relationship with usb.
> > > >
> > > > Could someone help on this? thanks.
> > >
> > > My question back to you is why are you doing this conversion?  Have you
> > > found that it is needed for something?  Are there problems in the -rt
> > > kernels that this conversion helps with?  Or is it just a janitorial
> > > "convert semaphore to mutex" type thing.
> >
> > Sorry for delay-reply because recently I have little free time.
> >
> > Mutex is lightweighter than semaphore, the device/class is used
> > heavily in kernel, so I think the convert would be worth.
>
> 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?
>
> All of the places this is used should be on a "slow" code-path, and the
> semaphores themselves should very rarely ever have to block anyone under
> normal usages.
>
> Without any real problems being reported for this, I wouldn't worry
> about this, the effort involved is non-trivial as you are quickly
> finding out :)
>

Maybe not a big problem, but AFAIK convertion is better.
For Benchmarks, not yet.

OTOH, as you said the effort to do this is indeed a problem.

Regards
dave

  parent reply	other threads:[~2008-01-02  5:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-29  1:01 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
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 [this message]
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=a8e1da0801012137n78a18654t2a9d40225f0e8e1a@mail.gmail.com \
    --to=hidave.darkstar@gmail.com \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --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

all inboxes | Powered by JetHome®