Wed Jun 27 20:43:00 CEST 2001
> This is kind of what I thought from the docs but crypto seems
> to do it a
> little differently.. Here there is a server process which
> opens the driver,
> "owns" it, and puts the port reference in a 'protected' ets
> table (i.e. read
> allowed by all). The client functions read this table and call
> erlang:port_command in the context of the *calling* process.
Hmm, I just made a driver which does both mechanisms and the one which does
port_control in the calling process averages 20uS per call but the one which
uses driver_output averages about 35uS.
NOTICE AND DISCLAIMER:
This email (including attachments) is confidential. If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents. We cannot accept liability for any breaches of
confidence arising through use of email. Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions. We will not accept responsibility for any commitments
made by our employees outside the scope of our business. We do not warrant
the accuracy or completeness of such information.
More information about the erlang-questions