> > On fc_disc_rport_callback(): I'm getting rid of that by
> > having the rport layer do the list maintenance.  Since
> > that's all that callback did, there isn't a need for it in fc_disc.
> > fc_lport still uses an rport event callback to find out when the
> > directory server rport or point-to-point rport is ready.
> > 
> > We could have a transport-template callback for all remote ports as
> > well if there's a need by LLDs.   That would be in addition to
> > the rport callback that was specified via rdata->ops, and we would
> > probably call that before the other one on create, and after the
> > other one on delete, I guess.
> > 
> Bhanu, do you want to override the callbacks completely or just be
> notified as well as letting the normal callback continue doing what
> they're currently doing?
> 
> 
I think it is good enough if the normal callback continues and LLD gets 
notified when a new rport is discovered or an existing rport is logged out.
_______________________________________________
devel mailing list
[email protected]
http://www.open-fcoe.org/mailman/listinfo/devel

Reply via email to