From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Patrick Mochel <mochel@digitalimplant.org>,
David Brownell <david-b@pacbell.net>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: klists and struct device semaphores
Date: Tue, 29 Mar 2005 11:26:17 -0500 [thread overview]
Message-ID: <d120d500050329082665855878@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0503291055560.1038-100000@ida.rowland.org>
On Tue, 29 Mar 2005 11:18:13 -0500 (EST), Alan Stern
<stern@rowland.harvard.edu> wrote:
>
> With that change in place we can guarantee that every time a USB driver's
> probe() is called, both the interface and the parent device are locked.
>
> I don't know how cleanly this can be implemented. You probably don't want
> to lock dev->parent->sem every time, only when needed. Maybe the simplest
> approach would be to add a flag in struct bus_type, which could be set for
> the USB bus_type and clear for everything else.
>
I think it is fine to lock parent unconditionally. After all
device/driver matching is not the most performance-critical part of
the kernel.
--
Dmitry
next prev parent reply other threads:[~2005-03-29 16:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 16:53 klists and struct device semaphores Alan Stern
2005-03-28 16:56 ` Patrick Mochel
2005-03-28 19:48 ` Alan Stern
2005-03-29 16:38 ` Patrick Mochel
2005-03-28 17:44 ` Patrick Mochel
2005-03-28 18:16 ` David Brownell
2005-03-28 18:43 ` Patrick Mochel
2005-03-28 21:58 ` Alan Stern
2005-03-31 2:12 ` Patrick Mochel
2005-03-31 16:18 ` Alan Stern
2005-03-31 17:59 ` Patrick Mochel
2005-03-31 18:18 ` David Brownell
2005-03-31 18:26 ` Patrick Mochel
2005-03-31 18:46 ` David Brownell
2005-03-31 19:08 ` Patrick Mochel
2005-03-31 19:08 ` Dmitry Torokhov
2005-03-29 16:18 ` Alan Stern
2005-03-29 16:26 ` Dmitry Torokhov [this message]
2005-03-31 2:16 ` Patrick Mochel
2005-03-31 3:01 ` Dmitry Torokhov
2005-03-31 5:47 ` Patrick Mochel
2005-03-31 16:24 ` Alan Stern
2005-03-31 18:04 ` Patrick Mochel
2005-03-31 19:49 ` Alan Stern
2005-04-02 18:06 ` Alan Stern
2005-04-06 7:39 ` Patrick Mochel
2005-04-06 19:45 ` Alan Stern
2005-04-07 20:08 ` Patrick Mochel
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=d120d500050329082665855878@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=david-b@pacbell.net \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=stern@rowland.harvard.edu \
/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