Cathy Zhou wrote:
> Paul Durrant wrote:
>> cc-ing reply to network-discuss since that's where most of the Nemo
>> (GLDv3 - I wish it was never called that, it's too confusing) folks
>> hang out...
>>
>> On 11/22/06, Garrett D'Amore <[EMAIL PROTECTED]> wrote:
>>> GLD  could achieve this by having the original DLPI message (e.g.
>>> DL_PROMISCON_REQ or DL_SET_PHYS_ADDR_REQ, or DL_GET_STATISTICS_REQ)
>>> spawn a task (on a taskq) to call the entry point.  This task would
>>> also
>>> be responsible for sending the reply message back upstream.
>>>
>>
>> With v3 a.k.a. Nemo, the mac layer processing is divorced from STREAMS
>> by the data-link services module (dls). This is a functional
>> interface, which I did at one point code up with the possibility of
>> handling async. completion but it just got too messy, and none of the
>> existing drivers were using it, so I pulled it out.
>> Do you know of any current or forthcoming h/w that would require the
>> ability to asynchronously complete operations?
>>
> I am not sure about the context, but as part of the Clearview project,
> the DLPI control messages processing path in GLDv3 has been changed to
> be async.
>
> Thanks
> - Cathy

That's great news!

-- 
Garrett D'Amore, Principal Software Engineer
Tadpole Computer / Computing Technologies Division,
General Dynamics C4 Systems
http://www.tadpolecomputer.com/
Phone: 951 325-2134  Fax: 951 325-2191

_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code

Reply via email to