From: Tejun Heo <tj@kernel.org>
To: Stephan Gatzka <stephan.gatzka@gmail.com>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux1394-devel@lists.sourceforge.net, peter@hurleysoftware.com,
linux-kernel@vger.kernel.org
Subject: Re: function call fw_iso_resource_mange(..) (core-iso.c) does not return
Date: Wed, 22 May 2013 18:22:34 +0900 [thread overview]
Message-ID: <20130522092234.GB3466@mtj.dyndns.org> (raw)
In-Reply-To: <24da2e78e684e560c5aa034cebd3e26b@gatzka.org>
Hello,
On Wed, May 22, 2013 at 11:08:43AM +0200, Stephan Gatzka wrote:
> >There is quite a bit going on in firewire-ohci's and
> >firewire-core's parts
> >of self-ID-complete event handling. But I suspect that stuff like
> >that is
> >still not in the league for which CPU_INTENSIVE was intended for
> >(cryptography etc.).
>
> Some advice from Tejun would be great here...
No need to use CPU_INTENSIVE unless it's really burning considerable
amount of CPU cycles. I don't know what the firewire work items are
doing but am pretty doubtful they would need the flag, and please
don't use it to work around deadlock problems. :)
Thanks.
--
tejun
next prev parent reply other threads:[~2013-05-22 9:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8ac7ca3200325ddf85ba57aa6d000f70@gatzka.org>
2013-05-21 20:28 ` Stefan Richter
2013-05-22 9:08 ` Stephan Gatzka
2013-05-22 9:22 ` Tejun Heo [this message]
2013-05-22 13:11 ` Stefan Richter
[not found] ` <519BA6AC.1080600@hurleysoftware.com>
2013-05-21 21:13 ` Stefan Richter
2013-05-22 8:53 ` Stephan Gatzka
2013-05-22 13:38 ` Peter Hurley
[not found] ` <62922216e6007f9ef83956e0ca202644@gatzka.org>
2013-05-21 21:53 ` Stefan Richter
2013-05-21 22:10 ` Peter Hurley
2013-05-22 8:52 ` Stephan Gatzka
[not found] ` <20130521231847.GA6985@mtj.dyndns.org>
2013-05-22 7:48 ` Stefan Richter
2013-05-22 8:59 ` Stephan Gatzka
2013-05-22 12:58 ` Stefan Richter
2013-05-22 13:06 ` Stephan Gatzka
2013-05-22 13:21 ` Peter Hurley
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=20130522092234.GB3466@mtj.dyndns.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=peter@hurleysoftware.com \
--cc=stefanr@s5r6.in-berlin.de \
--cc=stephan.gatzka@gmail.com \
/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®