To isolate the implementation of OpenSM from the specific access layer implementation the thread etc would be in the vendor layer. The code in OpenSM core will use a simpler API: provide a callback and context.
Eitan Zahavi
Design Technology Director
Mellanox Technologies LTD
Tel:+972-4-9097208
Fax:+972-4-9593245
P.O. Box 586 Yokneam 20692 ISRAEL
> -----Original Message-----
> From: Michael S. Tsirkin [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 18, 2005 1:39 AM
> To: Eitan Zahavi
> Cc: 'Hal Rosenstock'; Liran Sorani; Yael Kalka; [email protected]
> Subject: Re: User Level Events - request for support
>
> Quoting r. Eitan Zahavi <[EMAIL PROTECTED]>:
> > Subject: RE: User Level Events - request for support
> >
> > > Hal Wrote:
> > > The OpenSM vendor layer should be enhanced with an additional API for a
> > > local port state changed event (and take a flag for port down and port
> > > up).
> > >
> > > OpenSM could then take this event and handle it generically. This could
> > > be implemented for gen2 (OpenIB) and gen1 if the events can be generated
> > > from VAPI or whatever.
> > >
> >
> > Yes. I agree. We should have osm_vendor_api.h define some callback registration
> > function for the local port up/down event. I will implement the OpenSM code for
> > firing a sweep one the port is up.
> >
> > EZ
> >
> > Eitan Zahavi
> > Design Technology Director
> > Mellanox Technologies LTD
> > Tel:+972-4-9097208
> > Fax:+972-4-9593245
> > P.O. Box 586 Yokneam 20692 ISRAEL
>
> IMHO a function that blocks till there's an event would be a saner API
> since it matches what kernel can provide.
> opensm can always create a thread if it wants to get a callback
> asynchronously.
>
> --
> MST - Michael S. Tsirkin
_______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
