From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux1394-devel@lists.sourceforge.net
Cc: "Jarod Wilson" <jwilson@redhat.com>,
"Kristian Høgsberg" <krh@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: fw-sbp2: don't retry login or reconnect after unplug
Date: Sun, 27 Jan 2008 19:26:33 +0100 (CET) [thread overview]
Message-ID: <tkrat.b69dbd0ef9978d09@s5r6.in-berlin.de> (raw)
In-Reply-To: <tkrat.98202457f6ba93dd@s5r6.in-berlin.de>
I wrote:
> If a device is being unplugged while fw-sbp2 had a login or reconnect on
> schedule, it would take about half a minute to shut the fw_unit down:
>
> Jan 27 18:34:54 stein firewire_sbp2: logged in to fw2.0 LUN 0000 (0 retries)
> <unplug>
> Jan 27 18:34:59 stein firewire_sbp2: sbp2_scsi_abort
> Jan 27 18:34:59 stein scsi 25:0:0:0: Device offlined - not ready after error recovery
> Jan 27 18:35:01 stein firewire_sbp2: orb reply timed out, rcode=0x11
> Jan 27 18:35:06 stein firewire_sbp2: orb reply timed out, rcode=0x11
> Jan 27 18:35:12 stein firewire_sbp2: orb reply timed out, rcode=0x11
> Jan 27 18:35:17 stein firewire_sbp2: orb reply timed out, rcode=0x11
> Jan 27 18:35:22 stein firewire_sbp2: orb reply timed out, rcode=0x11
> Jan 27 18:35:27 stein firewire_sbp2: orb reply timed out, rcode=0x11
> Jan 27 18:35:32 stein firewire_sbp2: orb reply timed out, rcode=0x11
> Jan 27 18:35:32 stein firewire_sbp2: failed to login to fw2.0 LUN 0000
> Jan 27 18:35:32 stein firewire_sbp2: released fw2.0
>
> After this patch, typically only a few seconds spent in __scsi_add_device
> remain:
>
> Jan 27 19:05:50 stein firewire_sbp2: logged in to fw2.0 LUN 0000 (0 retries)
> <unplug>
> Jan 27 19:05:56 stein firewire_sbp2: sbp2_scsi_abort
> Jan 27 19:05:56 stein scsi 33:0:0:0: Device offlined - not ready after error recovery
> Jan 27 19:05:56 stein firewire_sbp2: released fw2.0
>
> The benefit of this is negligible on simple setups. But on buses with
> several devices, we should avoid any unnecessary blockade of fw-sbp2's
> workqueue thread.
There is an error in the last sentences. The time spent sleeping in
workqueue jobs is the same before and after. What this patch only
avoids are a few wasted CPU cycles, irritating log messages, and
needlessly prolonged lifetime of a few driver objects.
However, less noise in the syslog may already be enough justification
for this patch.
--
Stefan Richter
-=====-==--- ---= ==-==
http://arcgraph.de/sr/
next prev parent reply other threads:[~2008-01-27 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 18:14 Stefan Richter
2008-01-27 18:26 ` Stefan Richter [this message]
2008-01-28 16:26 ` Jarod Wilson
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=tkrat.b69dbd0ef9978d09@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=jwilson@redhat.com \
--cc=krh@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-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
Powered by JetHome