en Copyright 2015 Java http://172.16.0.5:8080/history/freebsd-14.2/sys/dev/isp/isp_stds.h#71625ec9 sys: Remove $FreeBSD$: one-line .c comment patternRemove /^/[*/]\s*\$FreeBSD\$.*\n/ List of files: /freebsd-14.2/sys/dev/isp/isp_stds.h Wed, 16 Aug 2023 17:54:24 +0000 Warner Losh <imp@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-14.2/sys/dev/isp/isp_stds.h#4d846d26 spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSDThe SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catchup to that fact and revert to their recommended match of BSD-2-Clause.Discussed with: pfgMFC After: 3 daysSponsored by: Netflix List of files: /freebsd-14.2/sys/dev/isp/isp_stds.h Wed, 10 May 2023 15:40:58 +0000 Warner Losh <imp@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-14.2/sys/dev/isp/isp_stds.h#88364968 Introduce support of SCSI Command Priority.SAM-3 specification introduced concept of Task Priority, that was renamedto Command Priority in SAM-4, and supported by all modern SCSI transports.It provides 15 levels of relative priorities: 1 - highest, 15 - lowest and0 - default. SAT specification for SATA devices translates priorities 1-3into NCQ high priority.This change adds new "priority" field into empty spots of struct ccb_scsiioand struct ccb_accept_tio of CAM and struct ctl_scsiio of CTL. Respectivesupport is added into iscsi(4), isp(4), mpr(4), mps(4) and ocs_fc(4) driversfor both initiator and where applicable target roles. Minimal support wasadded to CTL to receive the priority value from different frontends, pass itbetween HA controllers and report in few places.This patch does not add consumers of this functionality, so nothing shouldreally change yet, since the field is still set to 0 (default) on initiatorand not actively used on target. Those are to be implemented separately.I've confirmed priority working on WD Red SATA disks connected via mpr(4)and properly transferred to CTL target via iscsi(4), isp(4) and ocs_fc(4).While there, added missing tag_action support to ocs_fc(4) initiator role.MFC after: 1 monthRelnotes: yesSponsored by: iXsystems, Inc. List of files: /freebsd-14.2/sys/dev/isp/isp_stds.h Sun, 25 Oct 2020 19:34:02 +0000 Alexander Motin <mav@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-14.2/sys/dev/isp/isp_stds.h#6f9dbc0e Fix CRN resets in the isp(4) driver in certain situations.The Command Reference Number (CRN) is part of the FC-Tape featuresthat we enable when talking to tape drives. It starts at 1, andgoes to 255 and wraps around to 1. There are a number of resettype conditions that result in the CRN getting reset to 1. Theseare detailed in section 4.10 (table 8) of the FCP-4r02b specification.One of the conditions is when a PRLI (Process Login) is sent bythe initiator, and the Establish Image Pair bit is set in Word 0of the PRLI.Previously, the isp(4) driver core sent a notification viaisp_async() that the target had changed or stayed in place, butthere was no indication of whether a PRLI was sent and whether theEstablish Image Pair bit was set.The result of this was that in some situations, notablyswitching back and forth between a direct connection and a switchconnection to a tape drive, the isp(4) driver would fail to resetthe CRN in situations that require it according to the spec. Whenthe CRN isn't reset in a situation that requires it, the tape drivethen rejects every subsequent command that is sent to the drive.It is assuming that the commands are being sent out of order.So, modify the isp(4) driver to include Word 0 of the PRLI commandwhen it sends isp_async() notifications of target changes. Look atthe Establish Image Pair bit, and reset the CRN if that bit is set.With this change, I am able to switch a tape drive back and forthbetween a direct connection and a switch connection, and the isp(4)driver resets the CRN when it should.sys/dev/isp_stds.h: Add bit definitions for PRLI Word 0.sys/dev/ispmbox.h: Add PRLI Word 0 to the port database type, isp_pdb_t.sys/dev/ispvar.h Add PRLI Word 0 to fcportdb_t.sys/dev/isp.c: Populate the new prli_word0 parameter in the port database. In isp_pdb_add_update(), add a check to see if the Establish Image Pair bit is set in PRLI Word 0. If it is, then that is an additional reason to create a change notification.sys/dev/isp_freebsd.c: In isp_async(), if the device changed or stayed, look at PRLI Word 0 to see if the Establish Image Pair bit is set. If it is, reset the CRN if we haven't already.MFC after: 1 weekSponsored by: Spectra LogicDifferential Revision: https://reviews.freebsd.org/D19472 List of files: /freebsd-14.2/sys/dev/isp/isp_stds.h Mon, 11 Mar 2019 14:21:14 +0000 Kenneth D. Merry <ken@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-14.2/sys/dev/isp/isp_stds.h#718cf2cc sys/dev: further adoption of SPDX licensing ID tags.Mainly focus on files that use BSD 2-Clause license, however the tool Iwas using misidentified many licenses so this was mostly a manual - errorprone - task.The Software Package Data Exchange (SPDX) group provides a specificationto make it easier for automated tools to detect and summarize well knownopensource licenses. We are gradually adopting the specification, notingthat the tags are considered only advisory and do not, in any way,superceed or replace the license texts. List of files: /freebsd-14.2/sys/dev/isp/isp_stds.h Mon, 27 Nov 2017 14:52:40 +0000 Pedro F. Giffuni <pfg@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-14.2/sys/dev/isp/isp_stds.h#7e53e7ac Register symbolic port/node names in FC name server.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, butit is not passed here through CAM now.MFC after: 2 weeks List of files: /freebsd-14.2/sys/dev/isp/isp_stds.h Sat, 09 Apr 2016 14:50:47 +0000 Alexander Motin <mav@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-14.2/sys/dev/isp/isp_stds.h#92056a05 Register our FC4 Features in SNS. List of files: /freebsd-14.2/sys/dev/isp/isp_stds.h Tue, 17 Nov 2015 19:57:49 +0000 Alexander Motin <mav@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-14.2/sys/dev/isp/isp_stds.h#c98d2b1f Add partial support for QUERY TMF to CAM and isp(4).This change allows to decode respective functions in isp(4) in target modeand pass them through CAM to CTL. Unfortunately neither CAM nor isp(4)support returning response info for those task management functions now.On the other side I just have no initiator to test this functionality. List of files: /freebsd-14.2/sys/dev/isp/isp_stds.h Fri, 23 Oct 2015 18:34:18 +0000 Alexander Motin <mav@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-14.2/sys/dev/isp/isp_stds.h#387d8239 -----------MISC CHANGESAdd a new async event- ISP_TARGET_NOTIFY_ACK, that will guaranteeeventual delivery of a NOTIFY ACK. This is tons better than justignoring the return from isp_notify_ack and hoping for the best.Clean up the lower level lun enable code to be a bit more sensible.Fix a botch in isp_endcmd which was messing up the sense data.Fix notify ack for SRR to use a sensible error code in the caseof a reject.Clean up and make clear what kind of firmware we've loaded andwhat capabilities it has.-----------FULL (252 byte) SENSE DATAIn CTIOs for the ISP, there's only a limimted amount of spaceto load SENSE DATA for associated CHECK CONDITIONS (24 or 26bytes). This makes it difficult to send full SENSE DATA that canbe up to 252 bytes.Implement MODE 2 responses which have us build the FCP Responsein system memory which the ISP will put onto the wire directly.On the initiator side, the same problem occurs in that a commandstatus response only has a limited amount of space for SENSE DATA.This data is supplemented by status continuation responses thatthe ISP pushes onto the response queue after the status response.We now pull them all together so that full sense data can bereturned to the periph driver.This is supported on 23XX, 24XX and 25XX cards.This is also preparation for doing >16 byte CDBs.-----------FC TAPEImplement full FC-TAPE on both initiator and target mode side. Thiscapability is driven by firmware loaded, board type, board NVRAMsettings, or hint configuration options to enable or disable. Thisis supported for 23XX, 24XX and 25XX cards.On the initiator side, we pretty much just have to generate a commandreference number for each command we send out. This is FCP-4 compliantin that we do this per ITL nexus to generate the allowed 1 thru 255CRN.In order to support the target side of FC-TAPE, we now pay attentionto more of the PRLI word 3 parameters which will tell us whetheran initiator wants confirmed responses. While we're at it, we'llpay attention to the initiator view too and report it.On sending back CTIOs, we will notice whether the initiator wantsconfirmed responses and we'll set up flags to do so.If a response or data frame is lost the initiator sends us an SRR(Sequence Retransmit Request) ELS which shows up as an SRR notifyand all outstanding CTIOs are nuked with SRR Received status. TheSRR notify contains the offset that the initiator wants us to restartthe data transfer from or to retransmit the response frame.If the ISP driver still has the CCB around for which the data segmentor response applies, it will retransmit.However, we typically don't know about a lost data frame until wesend the FCP Response and the initiator totes up counters for datamoved and notices missing segments. In this case we've alreadycompleted the data CCBs already and sent themn back up to the periphdriver. Because there's no really clean mechanism yet in CAM tohandle this, a hack has been put into place to complete the CTIOCCB with the CAM_MESSAGE_RECV status which will have a MODIFY DATAPOINTER extended message in it. The internal ISP target groks thisand ctl(8) will be modified to deal with this as well.At any rate, the data is retransmitted and an an FCP response issent. The whole point here is to successfully complete a commandso that you don't have to depend on ULP (SCSI) to have to recover,which in the case of tape is not really possible (hence the nameFC-TAPE).Sponsored by: SpectralogicMFC after: 1 month List of files: /freebsd-14.2/sys/dev/isp/isp_stds.h Sat, 28 Jul 2012 20:06:29 +0000 Matt Jacob <mjacob@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-14.2/sys/dev/isp/isp_stds.h#7733cf8f MFC a number of changes from head for ISP (203478,203463,203444,202418,201758,201408,201325,200089,198822,197373,197372,197214,196162). Since one of thosechanges was a semicolon cleanup from somebody else, this touches a lot more. List of files: /freebsd-14.2/sys/dev/isp/isp_stds.h Thu, 11 Feb 2010 18:34:06 +0000 Matt Jacob <mjacob@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-14.2/sys/dev/isp/isp_stds.h#cb8461c8 (semiforced commit to add comment missed in last delta)Add a maximum response length for FCP RSPNS IUs.Clarify some of the FC option words for setting parametersand try and disable automatic PRLI when in target mode- thisshould correct some cases of N-port topologies with 23XX cardswhere we put out an illegal PRLI (in target mode only we'renot supposed to put out a PRLI). List of files: /freebsd-14.2/sys/dev/isp/isp_stds.h Mon, 21 Sep 2009 01:41:19 +0000 Matt Jacob <mjacob@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-14.2/sys/dev/isp/isp_stds.h#e3ec25e2 Remove file unused in freebsd. List of files: /freebsd-14.2/sys/dev/isp/isp_stds.h Mon, 21 Sep 2009 01:38:22 +0000 Matt Jacob <mjacob@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-14.2/sys/dev/isp/isp_stds.h#2df76c16 Add 8Gb support (isp_2500). Fix a fair number of configuration andfirmware loading bugs.Target mode support has received some serious attention to make itmore usable and stable.Some backward compatible additions to CAM have been made that maketarget mode async events easier to deal with have also been putinto place.Further refinement and better support for NP-IV (N-port Virtualization)is now in place.Code for release prior to RELENG_7 has been stripped away for code clarity.Sponsored by: Copan SystemsReviewed by: scottl, ken, jung-uk kimApproved by: re List of files: /freebsd-14.2/sys/dev/isp/isp_stds.h Sat, 01 Aug 2009 01:04:26 +0000 Matt Jacob <mjacob@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-14.2/sys/dev/isp/isp_stds.h#e48b2487 Fix some stupid copyright mistakes that have been there for quite some time. List of files: /freebsd-14.2/sys/dev/isp/isp_stds.h Sat, 10 Mar 2007 02:39:54 +0000 Matt Jacob <mjacob@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-14.2/sys/dev/isp/isp_stds.h#f7c631bc Push things closer to path failover by implementing loop down andgone device timers and zombie state entries. There are tunablesthat can be used to select a number of parameters.loop_down_limit - how long to wait for loop to come back up beforedeclaringall devices dead (default 300 seconds)gone_device_time- how long to wait for a device that has appearedto leave the loop or fabric to reappear (default 30 seconds)Internal tunables include (which should be externalized):quick_boot_time- how long to wait when booting for loop to come upchange_is_bad- whether or not to accept devices with the sameWWNN/WWPN that reappear at a different PortID as being the 'same'device.Keen students of some of the subtle issues here will ask howone can keep devices from being re-accepted at all (the answeris to set a gone_device_time to zero- that effectively wouldbe the same thing). List of files: /freebsd-14.2/sys/dev/isp/isp_stds.h Tue, 14 Nov 2006 08:45:48 +0000 Matt Jacob <mjacob@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-14.2/sys/dev/isp/isp_stds.h#10365e5a Add 4Gb (24XX) support and lay the foundation for a lot of new stuff. List of files: /freebsd-14.2/sys/dev/isp/isp_stds.h Thu, 02 Nov 2006 03:21:32 +0000 Matt Jacob <mjacob@FreeBSD.org>