From owner-freebsd-scsi Wed Nov 20 13:18:41 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC57A37B404 for ; Wed, 20 Nov 2002 13:18:40 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 4E29E43E97 for ; Wed, 20 Nov 2002 13:18:40 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 65034 invoked by uid 1000); 20 Nov 2002 21:18:41 -0000 Date: Wed, 20 Nov 2002 13:18:41 -0800 (PST) From: Nate Lawson To: Chuck Tuffli Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SIM as loadable module? In-Reply-To: <20021120195956.GB35733@cre85086tuf.rose.agilent.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 20 Nov 2002, Chuck Tuffli wrote: > On Tue, Nov 19, 2002 at 11:06:04AM -0800, Nate Lawson wrote: > > fcPortGetInfo?). I guess your approach should be necessary in the FC case > > since your position in the chain can change when you get a LIP. > > Wouldn't the driver want to insulate the CAM from this kind of event? > I was thinking that the CAM's view of TID should be independent from > FC's view of NPort_ID. The intent would be that the WWN of TID x > should be the same before and after a LIP, but the mapping of TID to > NPort_ID may change. You might want to check with Matt. IIRC, isp allows target order to change when a LIP occurs. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message