FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F11.3.0 2018-03-29T02:50:57Z 2018-03-29T02:50:57Z Eitan Adler eadler@FreeBSD.org 2018-03-29T02:50:57Z urn:sha1:4ab2e064d7950be84256d671a7ae93f87cc6aa36 This was intended to be a non-functional change. It wasn't. The commit message was thus wrong. In addition it broke arm, and merged crypto related code. Revert with prejudice. This revert skips files touched in r316370 since that commit was since MFCed. This revert also skips files that require $FreeBSD$ property changes. Thank you to those who helped me get out of this mess including but not limited to gonzo, kevans, rgrimes. Requested by: gjb (re) 2018-03-14T03:19:51Z Eitan Adler eadler@FreeBSD.org 2018-03-14T03:19:51Z urn:sha1:be5d0b9566b13fdf8cabebb63334cbec12bfc409 These changes are incomplete but are making it difficult to determine what other changes can/should be merged. No objections from: pfg 2017-08-01T13:03:06Z Alexander Motin mav@FreeBSD.org 2017-08-01T13:03:06Z urn:sha1:dbce1d6f1e873df045be0ca10e8ceb72e1592981 Switch fabric scans from GID_FT to GID_PT+GFF_ID/GFT_ID. Instead of using GID_FT SNS request to get list of registered FCP ports, use GID_PT to get list of all Nx_Ports, and then use GFF_ID and/or GFT_ID requests to find whether they are FCP and target capable. The problem with old approach is that GID_FT does not report ports without FC-4 type registered. In particular it was impossible to boot OS from FreeBSD FC target using QLogic FC BIOS, since one does not register FC-4 type even on new cards and so ignored by old code as incompatible. As a side bonus this allows initiator to skip pointless logins to other initiators by fetching that information from SNS instead. In case some switches do not implement GFF_ID/GFT_ID correctly, add sysctls to disable that functionality. I handled broken GFF_ID of my Brocade 200E, but there may be other switches with different bugs. Linux also uses GID_PT, but GFF_ID is disabled by default there, and GFT_ID is not supported. Sponsored by: iXsystems, Inc. 2017-04-24T10:21:13Z Alexander Motin mav@FreeBSD.org 2017-04-24T10:21:13Z urn:sha1:5f1be74b8c73e029fcffcdb031cad43bddf08217 The code is so alike that it is pointless to keep it separate. 2017-03-29T15:57:50Z Alexander Motin mav@FreeBSD.org 2017-03-29T15:57:50Z urn:sha1:e52abb371c21c9adf2f18b8c7d85097758ef48e9 2017-03-28T10:11:00Z Alexander Motin mav@FreeBSD.org 2017-03-28T10:11:00Z urn:sha1:fe5b8d4638e580c46316db70ab3ae0aa87383b60 This change fixes DMA resource leak on driver unload. Also it removes DMA resources allocation for hardcoded number of requests before fetching the real number from firmware. Also it prepares ground for more flexible IRQs allocation according to firmware capabilities. 2016-04-09T14:50:47Z Alexander Motin mav@FreeBSD.org 2016-04-09T14:50:47Z urn:sha1:7e53e7accc063b59d0d653d6b3229b71a2850228 This is cosmetics that simplifies identification of new ports on FC switch. It would be good to use target name from CTL here instead of hostname, but it is not passed here through CAM now. MFC after: 2 weeks 2015-12-25T13:03:18Z Alexander Motin mav@FreeBSD.org 2015-12-25T13:03:18Z urn:sha1:970ceb2fd5b6f3dca91783865b1b0242d3077d2c I am not sure why this was split long ago, but I see no reason for it. At this point this unification just slightly reduces memory usage, but as next step I plan to reuse shared handle space for other IOCB types. 2015-12-25T03:44:29Z Alexander Motin mav@FreeBSD.org 2015-12-25T03:44:29Z urn:sha1:a4f43c01c0719339ac6b348c93a061f35d47e096 Previously it was done only on full chip reinit, that caused old ports resurrect in case of virtual port reenabling. 2015-11-23T10:06:19Z Alexander Motin mav@FreeBSD.org 2015-11-23T10:06:19Z urn:sha1:3e6deb330e6613bcd7b3ec227add1eb2a2dcaaf8 Hacks to enable target mode there complicated code, while didn't really work. And for outdated hardware fixing it is not really interesting. Initiator mode tested with Qlogic 1080 adapter is still working fine.