public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Duncan Sands <baldrick@free.fr>
Cc: Greg KH <greg@kroah.com>,
	linux-usb-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, Frederic Detienne <fd@cisco.com>
Subject: Re: [linux-usb-devel] [PATCH 1/9] USB usbfs: take a reference to the usb device
Date: Mon, 19 Apr 2004 10:25:18 -0700	[thread overview]
Message-ID: <40840B7E.4080605@pacbell.net> (raw)
In-Reply-To: <200404172217.10994.baldrick@free.fr>

Heh ... I like this, getting rid of more of locks from usbcore.


Duncan Sands wrote:
>   In later steps we can
> (1) turn dev->serialize into a rwsem

That doesn't bother me (unlike some folk!) but I do
agree it should wait until the rest shakes out, and
until we can observe benefits.  Hardly any code paths
need complete mutual exclusion (writelock).


> (2) push the acquisition of dev->serialize down to the lower levels as they are fixed up.

Actually at least some of those lower levels are getting
fixed by pushing the lock acquisition up.

The reason usbfs needs to get involved in that stuff is
that it's going around the standard usb driver structure.
One of the other things that "usbfs2" should do is act a
lot more like a "normal" device driver, so it plays better
with more of the normal usbcore mechanisms.

- Dave



  parent reply	other threads:[~2004-04-19 17:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-14 10:29 [PATCH 1/9] USB usbfs: take a reference to the usb device Duncan Sands
2004-04-17 20:17 ` [linux-usb-devel] " Duncan Sands
2004-04-17 20:33   ` Oliver Neukum
2004-04-18  9:35     ` Duncan Sands
2004-04-18 13:57       ` Oliver Neukum
2004-04-18 14:08         ` Duncan Sands
2004-04-18 14:40       ` Alan Stern
2004-04-19 17:25   ` David Brownell [this message]
2004-04-23 23:18 ` Greg KH
2004-04-26 14:05   ` Duncan Sands
2004-04-26 22:14     ` Greg KH
2004-04-27  8:58       ` [linux-usb-devel] " Oliver Neukum
2004-04-30  9:04         ` Duncan Sands
2004-05-01 23:01           ` Greg KH

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=40840B7E.4080605@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=baldrick@free.fr \
    --cc=fd@cisco.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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