From: Dan Williams <dan.j.williams@intel.com>
To: James Bottomley <James.Bottomley@suse.de>
Cc: "Jiang, Dave" <dave.jiang@intel.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
David Milburn <dmilburn@redhat.com>,
"Danecki, Jacek" <jacek.danecki@intel.com>,
"jack_wang@usish.com" <jack_wang@usish.com>,
"lindar_liu@usish.com" <lindar_liu@usish.com>,
"Skirvin, Jeffrey D" <jeffrey.d.skirvin@intel.com>,
"Nadolski, Edmund" <edmund.nadolski@intel.com>,
Srinivas <satyasrinivasp@hcl.in>
Subject: Re: [PATCH] libsas: flush initial device discovery before completing ->scan_finished()
Date: Fri, 18 Feb 2011 17:32:42 -0800 [thread overview]
Message-ID: <1298079162.19161.84.camel@dwillia2-linux> (raw)
In-Reply-To: <1298073759.3007.216.camel@mulgrave.site>
On Fri, 2011-02-18 at 16:02 -0800, James Bottomley wrote:
> On Wed, 2011-02-16 at 19:06 -0800, Dan Williams wrote:
> > During initial scan libsas drivers start their phys and notify libsas
> > with PORTE_BYTES_DMAED events as port links are established. This
> > notification in turn causes libsas to post DISCE_DISCOVER_DOMAIN events
> > to the queue. Calling scsi_flush_work() at the end of scan_finished
> > guarantees that all preceding PORTE_BYTES_DMAED events have been
> > registered in the queue, but it does not guarantee that the resulting
> > DISCE_DISCOVER_DOMAIN events have been processed because
> > flush_workqueue() explicitly avoids live-locking with incoming work.
> >
> > Introduce sas_flush_discovery() to guarantee that all initial discovery
> > events have completed. It is called after the driver determines all
> > initial PORTE_BYTES_DMAED events have had a chance to enter the queue.
> > This does not cover BCNs that are generated during expander bring up,
> > only the initial sas_discover_domain() event.
>
> I think this is a workaround for an old bug in workqueue flushing (the
> flush doesn't clean work it causes) ... I thought that's been fixed for
> ages (well, months at least) ... have you verified that this is still a
> problem?
>
Hmm... I saw this initially on 2.6.36.
Latest git still has the "livelock" comment [1], and I was the able to
capture the following trace with two disks connected on a 2.6.38-rc5
build. The second "sas_discover_domain" completion occurs after the
"first flush done".
# tracer: nop
#
# TASK-PID CPU# TIMESTAMP FUNCTION
# | | | | |
<...>-5 [007] 93.849947: sas_porte_bytes_dmaed: sas_porte_bytes_dmaed: done
<...>-5 [007] 94.444643: sas_discover_domain: sas_discover_domain: complete
<...>-5 [007] 94.451993: sas_porte_bytes_dmaed: sas_porte_bytes_dmaed: done
<...>-1792 [006] 94.452011: isci_host_scan_finished: isci_host_scan_finished: first flush done
<...>-5 [007] 94.773256: sas_discover_domain: sas_discover_domain: complete
<...>-1792 [006] 94.773270: isci_host_scan_finished: isci_host_scan_finished: second flush done
--
Dan
[1]: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=kernel/workqueue.c;h=11869faa;hb=HEAD#l2201
prev parent reply other threads:[~2011-02-19 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 3:06 [PATCH] libsas: flush initial device discovery before completing ->scan_finished() Dan Williams
2011-02-19 0:02 ` James Bottomley
2011-02-19 1:32 ` Dan Williams [this message]
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=1298079162.19161.84.camel@dwillia2-linux \
--to=dan.j.williams@intel.com \
--cc=James.Bottomley@suse.de \
--cc=dave.jiang@intel.com \
--cc=dmilburn@redhat.com \
--cc=edmund.nadolski@intel.com \
--cc=jacek.danecki@intel.com \
--cc=jack_wang@usish.com \
--cc=jeffrey.d.skirvin@intel.com \
--cc=lindar_liu@usish.com \
--cc=linux-scsi@vger.kernel.org \
--cc=satyasrinivasp@hcl.in \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.