From: Timur Tabi <timur@freescale•com>
To: Qiang Liu <qiang.liu@freescale•com>
Cc: Vinod Koul <vinod.koul@intel•com>,
herbert@gondor•hengli.com.au, linux-crypto@vger•kernel.org,
Dan Williams <dan.j.williams@intel•com>,
linuxppc-dev@lists•ozlabs.org, davem@davemloft•net
Subject: Re: [linuxppc-release] [PATCH v2 4/4] fsl-dma: use spin_lock_bh to instead of spin_lock_irqsave
Date: Wed, 11 Jul 2012 10:01:01 -0500 [thread overview]
Message-ID: <4FFD952D.8040201@freescale.com> (raw)
In-Reply-To: <1341997326-18495-1-git-send-email-qiang.liu@freescale.com>
Qiang Liu wrote:
> Use spin_lock_bh to instead of spin_lock_irqsave for improving performance.
Please provide some evidence that performance has improved, as well as an
explanation why it's okay to use spin_lock_bh, and why it's faster.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-07-11 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 9:02 [PATCH v2 4/4] fsl-dma: use spin_lock_bh to instead of spin_lock_irqsave Qiang Liu
2012-07-11 15:01 ` Timur Tabi [this message]
2012-07-12 9:07 ` [linuxppc-release] " Liu Qiang-B32616
2012-07-12 18:23 ` Timur Tabi
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=4FFD952D.8040201@freescale.com \
--to=timur@freescale$(echo .)com \
--cc=dan.j.williams@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=herbert@gondor$(echo .)hengli.com.au \
--cc=linux-crypto@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=qiang.liu@freescale$(echo .)com \
--cc=vinod.koul@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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