Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1251501
| From | John Garry <john.garry@huawei.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 13/25] scsi: hisi_sas: add path from phyup irq to SAS framework |
| Date | 2015-10-20 11:30 +0200 |
| Message-ID | <qlBp0-7Wo-3@gated-at.bofh.it> (permalink) |
| References | <qiN3k-2LY-27@gated-at.bofh.it> <qljBM-70Q-1@gated-at.bofh.it> <qlk4O-7Aj-7@gated-at.bofh.it> <qlAMh-6Wk-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
>> We could create a work_struct for each event, which would be fine. > > Yes, that would be the normal way to do it. You initialize the work > structures from the initial probe function to have the right > callbacks, and then you just queue the right one when you need to > defer an event. > > How many different events are there? > We currently only support processing 2 events in the workqueue: phy up and control phy. However we may want to use more in the future, like hotplug (for phy down) event. >> However we would sometimes still need some way of passing data to >> the event, like the phy control example. > > Do you mean the 'int func' argument to hisi_sas_control_phy_work? Yes > It sounds like that would again just be more different work_structs. > > At some point that might get silly (having 10 or more work structs > per phy), but then you could restructure the code to use something > other that work queues to get from interrupt context to process > context, e.g. a threaded interrupt handler. I'll check on this. We need to consider how to pass the argument for the control phy case. > > Note that the current code is not only unusual but also fragile > because you rely on GFP_ATOMIC memory allocations from the interrupt > handler, and they tend to eventually fail. Understood. For what it's worth, I was just following other SAS drivers as a refernce: see pm8001_handle_event() and mvs_handle_event() > > Arnd -- To unsubscribe from this list: send the line "unsubscribe > linux-scsi" in the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > > . > Thanks, John -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH 13/25] scsi: hisi_sas: add path from phyup irq to SAS framework John Garry <john.garry@huawei.com> - 2015-10-19 16:20 +0200
Re: [PATCH 13/25] scsi: hisi_sas: add path from phyup irq to SAS framework Arnd Bergmann <arnd@arndb.de> - 2015-10-19 16:30 +0200
Re: [PATCH 13/25] scsi: hisi_sas: add path from phyup irq to SAS framework John Garry <john.garry@huawei.com> - 2015-10-19 17:00 +0200
Re: [PATCH 13/25] scsi: hisi_sas: add path from phyup irq to SAS framework Arnd Bergmann <arnd@arndb.de> - 2015-10-20 10:50 +0200
Re: [PATCH 13/25] scsi: hisi_sas: add path from phyup irq to SAS framework John Garry <john.garry@huawei.com> - 2015-10-20 11:30 +0200
csiph-web