From: Hannes Reinecke <hare@suse.de>
To: Jason Yan <yanaijie@huawei.com>,
martin.petersen@oracle.com, jejb@linux.vnet.ibm.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
john.garry@huawei.com, zhaohongjiang@huawei.com, hare@suse.com,
dan.j.williams@intel.com, jthumshirn@suse.de,
Raj.Dinesh@microsemi.com, hch@lst.de, huangdaode@hisilicon.com,
chenxiang66@hisilicon.com, xiyou.wangcong@gmail.com,
Ewan Milne <emilne@redhat.com>, Tomas Henzl <thenzl@redhat.com>
Subject: Re: [PATCH v5 7/7] scsi: libsas: notify event PORTE_BROADCAST_RCVD in sas_enable_revalidation()
Date: Fri, 15 Dec 2017 13:26:14 +0100 [thread overview]
Message-ID: <9025ef90-943c-3682-a818-e84ad770c8dd@suse.de> (raw)
In-Reply-To: <20171208094210.24887-8-yanaijie@huawei.com>
On 12/08/2017 10:42 AM, Jason Yan wrote:
> There are two places queuing the disco event DISCE_REVALIDATE_DOMAIN.
> One is in sas_porte_broadcast_rcvd() and uses sas_chain_event() to queue
> the event. The other is in sas_enable_revalidation() and uses
> sas_queue_event() to queue the event. We have diffrent work queues for
> event and discovery now, so the DISCE_REVALIDATE_DOMAIN event may be
> processed in both event queue and discovery queue.
>
> Now since we do synchronous event handling, we cannot do it in discovery
> queue, so have to trigger a fake broadcast event to re-trigger the
> revalidation from event queue.
>
> Signed-off-by: Jason Yan <yanaijie@huawei.com>
> CC: John Garry <john.garry@huawei.com>
> CC: Johannes Thumshirn <jthumshirn@suse.de>
> CC: Ewan Milne <emilne@redhat.com>
> CC: Christoph Hellwig <hch@lst.de>
> CC: Tomas Henzl <thenzl@redhat.com>
> CC: Dan Williams <dan.j.williams@intel.com>
> ---
> drivers/scsi/libsas/sas_event.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/libsas/sas_event.c b/drivers/scsi/libsas/sas_event.c
> index 8c82c00..ae923eb 100644
> --- a/drivers/scsi/libsas/sas_event.c
> +++ b/drivers/scsi/libsas/sas_event.c
> @@ -116,11 +116,17 @@ void sas_enable_revalidation(struct sas_ha_struct *ha)
> struct asd_sas_port *port = ha->sas_port[i];
> const int ev = DISCE_REVALIDATE_DOMAIN;
> struct sas_discovery *d = &port->disc;
> + struct asd_sas_phy *sas_phy;
>
> if (!test_and_clear_bit(ev, &d->pending))
> continue;
>
> - sas_queue_event(ev, &d->disc_work[ev].work, ha);
> + if (list_empty(&port->phy_list))
> + continue;
> +
> + sas_phy = container_of(port->phy_list.next, struct asd_sas_phy,
> + port_phy_el);
> + ha->notify_port_event(sas_phy, PORTE_BROADCAST_RCVD);
> }
> mutex_unlock(&ha->disco_mutex);
> }
>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2017-12-15 12:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 9:42 [PATCH v5 0/7] Enhance libsas hotplug feature Jason Yan
2017-12-08 9:42 ` [PATCH v5 1/7] scsi: libsas: Use dynamic alloced work to avoid sas event lost Jason Yan
2017-12-15 12:14 ` Hannes Reinecke
2017-12-08 9:42 ` [PATCH v5 2/7] scsi: libsas: shut down the PHY if events reached the threshold Jason Yan
2017-12-15 12:18 ` Hannes Reinecke
2018-01-08 7:38 ` Hannes Reinecke
2017-12-08 9:42 ` [PATCH v5 3/7] scsi: libsas: make the event threshold configurable Jason Yan
2017-12-08 12:09 ` John Garry
2017-12-15 12:19 ` Hannes Reinecke
2018-01-04 10:04 ` John Garry
2017-12-08 9:42 ` [PATCH v5 4/7] scsi: libsas: Use new workqueue to run sas event and disco event Jason Yan
2017-12-15 12:20 ` Hannes Reinecke
2017-12-08 9:42 ` [PATCH v5 5/7] scsi: libsas: use flush_workqueue to process disco events synchronously Jason Yan
2017-12-15 12:21 ` Hannes Reinecke
2017-12-08 9:42 ` [PATCH v5 6/7] scsi: libsas: direct call probe and destruct Jason Yan
2017-12-15 12:23 ` Hannes Reinecke
2017-12-08 9:42 ` [PATCH v5 7/7] scsi: libsas: notify event PORTE_BROADCAST_RCVD in sas_enable_revalidation() Jason Yan
2017-12-15 12:26 ` Hannes Reinecke [this message]
2018-01-02 11:06 ` [PATCH v5 0/7] Enhance libsas hotplug feature John Garry
2018-01-04 6:01 ` Martin K. Petersen
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=9025ef90-943c-3682-a818-e84ad770c8dd@suse.de \
--to=hare@suse.de \
--cc=Raj.Dinesh@microsemi.com \
--cc=chenxiang66@hisilicon.com \
--cc=dan.j.williams@intel.com \
--cc=emilne@redhat.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=huangdaode@hisilicon.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=john.garry@huawei.com \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=thenzl@redhat.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yanaijie@huawei.com \
--cc=zhaohongjiang@huawei.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®