mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Luiz Fernando Capitulino <lcapitulino@mandriva.com.br>
To: Arjan van de Ven <arjan@infradead.org>
Cc: oliver@neukum.org, linux-usb-devel@lists.sourceforge.net,
	ehabkost@mandriva.com, gregkh@suse.de,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: [PATCH 00/10] usb-serial: Switches from spin lock to atomic_t.
Date: Wed, 7 Dec 2005 10:41:24 -0200	[thread overview]
Message-ID: <20051207104124.652237fb.lcapitulino@mandriva.com.br> (raw)
In-Reply-To: <1133958878.2869.21.camel@laptopd505.fenrus.org>

On Wed, 07 Dec 2005 13:34:38 +0100
Arjan van de Ven <arjan@infradead.org> wrote:

| On Wed, 2005-12-07 at 10:30 -0200, Luiz Fernando Capitulino wrote:
| > On Wed, 07 Dec 2005 13:27:13 +0100
| > Arjan van de Ven <arjan@infradead.org> wrote:
| > 
| > | 
| > | >  Isn't it right? Is the URB write so fast that switching to atomic_t
| > | > doesn't pay-off?
| > | 
| > | an atomic_t access and a spinlock are basically the same price... so
| > | what's the payoff ?
| > 
| >  One lock less,
| 
| where? 

 In the 'usb_serial_port', my patch number nine removes the spin lock.

| spin_unlock in principle runs unlocked on x86 at least
| (except for ppro workarounds but those are/should be optional)
| 
| 


-- 
Luiz Fernando N. Capitulino

  reply	other threads:[~2005-12-07 12:41 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-06 11:56 Luiz Fernando Capitulino
2005-12-06 19:40 ` Greg KH
2005-12-06 20:13   ` Eduardo Pereira Habkost
2005-12-06 22:48     ` [linux-usb-devel] " Oliver Neukum
2005-12-07 12:24       ` Luiz Fernando Capitulino
2005-12-07 12:27         ` Arjan van de Ven
2005-12-07 12:30           ` Luiz Fernando Capitulino
2005-12-07 12:34             ` Arjan van de Ven
2005-12-07 12:41               ` Luiz Fernando Capitulino [this message]
2005-12-07 12:54                 ` Luiz Fernando Capitulino
2005-12-07 15:07       ` Alan Stern
2005-12-07 15:22         ` Arjan van de Ven
2005-12-07 15:37           ` Oliver Neukum
2005-12-07 15:40             ` Arjan van de Ven
2005-12-07 15:50               ` Oliver Neukum
2005-12-07 16:02                 ` Alan Cox
2005-12-07 16:00           ` Eduardo Pereira Habkost
2005-12-07 16:02             ` Arjan van de Ven
2005-12-07 16:23               ` Eduardo Pereira Habkost
2005-12-07 16:01           ` Alan Stern
2005-12-07 16:04             ` Arjan van de Ven
2005-12-07 15:32         ` linux-os (Dick Johnson)
2005-12-07 16:08           ` Alan Stern
2005-12-06 20:14   ` Luiz Fernando Capitulino
2005-12-06 21:02     ` Pete Zaitcev
2005-12-06 21:18       ` Luiz Fernando Capitulino
2005-12-06 22:36         ` [linux-usb-devel] " Oliver Neukum
2005-12-07 12:25           ` Luiz Fernando Capitulino
2005-12-07 13:01             ` Oliver Neukum
2005-12-07 13:17               ` Luiz Fernando Capitulino
2005-12-07 16:41 ` Greg KH
2005-12-07 16:51   ` Luiz Fernando Capitulino
2005-12-07 17:13     ` Eduardo Pereira Habkost
2005-12-07 17:56       ` Greg KH
2005-12-07 19:10         ` Eduardo Pereira Habkost
2005-12-07 16:55   ` Otavio Salvador
2005-12-07 16:59     ` 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=20051207104124.652237fb.lcapitulino@mandriva.com.br \
    --to=lcapitulino@mandriva.com.br \
    --cc=arjan@infradead.org \
    --cc=ehabkost@mandriva.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=oliver@neukum.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®