Rao Shoaib wrote:
> Thanks Jim. We currently have two consumers that could use a plugin
> capability, NL7C and KSSL.
Btw, one of the consumers using raw IP with TPI is a product from
WhiteSands. They use it to do introspection of loopback traffic in one
of their analysis products. This product is used to help provide
observability/perf. analysis with client/server database products like
Oracle.
(I know this product exists, because I wrote the TPI shim module on a
contract a few years ago. I don't know if their solution works on
Nevada or S10 - at the time only Solaris 8 was important to them.)
Upshot of this is that I think both interposition (required e.g. for
security products) as well as introspection (required for products like
the one above) are desired. Some kind of hook to plugin alternate
function pointers is, IMO, an elegant way to do it. As much as STREAMs
is a performance loser, STREAMs is architecturally "beautiful", IMO. I
can think of no other solution (at least not in the other Unices and
workalikes I have experience with) which handles these needs as elegantly.
-- Garrett
>
> Rao.
>
>
>
> James Carlson wrote:
>> The DACF facility that Garrett was referring to is configured in
>> /etc/dacf.conf and is implemented in $SRC/uts/common/os/dacf.c.
>>
>> See "Extensions to Device Autoconfiguration" (PSARC 1998/212).
>>
>> It does look like the kind of mechanism that could create layered
>> drivers fairly nicely, though it's unclear how applicable that might
>> be for the Volo design.
>>
>> (I'd suggest omitting a layered interface until there's a consumer on
>> the horizon with specific needs. It's going to be very hard to design
>> some sort of plug-in interface without a specific target application
>> in mind.)
>>
>>
>
