[EMAIL PROTECTED] wrote: > From: Mike Christie <[EMAIL PROTECTED]> > > This is a first stab at removing the libfc dummy rport code > and private remote port code in other drivers. I am just sending the > fc class code to make sure I have the basic idea right. > > JamesS had presented two possible solutions for how to deal > with rports that exist and how to resolve dd_data state: > http://www.open-fcoe.org/pipermail/devel/2008-July/000401.html > > In one proposal we could have the LLD call some fc class > helpers to find existing rports by wwpn/wwnn. And the > alternative, is to try and make fc_remote_port_add figure > things out and call back into the LLD. > > I went with the former, because some of the issues like how to handle > if the class finds a rport with a matching port_id that is not in the > blocked state gets complicated from a callback. > > This patch was made over scsi-misc, becuase there are some patches > in there not in the fcoe tree. You can pull his tree into the fcoe > one and apply the patch. >
Oh yeah, this patch subject should have said RFC. The patch is only compile tested. I was using a qla2xxx fcoe card, and just got some cards to test/run libfc san code patches (the ptp ones are sort of busted again). _______________________________________________ devel mailing list [email protected] http://www.open-fcoe.org/mailman/listinfo/devel
