| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 803.1 | Maybe | STAR::GILLUM | Kirt Gillum | Tue Dec 01 1992 14:03 | 8 |
|
All OpenVMS LAN drivers use the LAN Class driver. There are some
architectural differences between FDDI and Ethernet, but the interface
is largely the same (i.e., most Ethernet applications will be able to
use FDDI without modification).
Is there anything specific you're looking for?
|
| 803.2 | some trivia | STAR::GAGNE | David Gagne - VMS/LAN Development | Wed Dec 02 1992 00:21 | 14 |
| Before V5.4-3, VMS only had the Ethernet drivers - and we had a module
called ETHERNET_CMN_RTN.MAR which was compiled and then linked into
each of the Ethernet drivers. All of the drivers (and the Ethernet
common routines) are in the COMM_DRIVER facility before V5.4-3.
As of VMS V5.4-3 (and ALPHA VMS V1.0), we have FDDI and Ethernet. So the
name of the source has changed to LAN.MAR and it is compiled into both
CSMACD.OBJ (which is linked into all the Ethernet drivers) and FDDI.OBJ
(which is linked into all the FDDI drivers). As of V5.4-3, the drivers
and the common routines are in the PHV_LAN facility. On ALPHA VMS,
they are in the LAN facility.
So we no longer call this the "Ethernet common routines". We now call
this code the LAN module or the LAN common routines.
|
| 803.3 | FXDRIVER and FFI > VCI? | CGOOA::PINTER | Just the VAX, ma'am. Just the VAX | Wed Dec 09 1992 13:35 | 23 |
| Thanks for the insights, and tangentially related:
Would someone please clarify the use of FFI interface with FDDI on VMS 5.5-2?
Specifically, we must have ~45Mbps on FDDI using *socket level TCP programming*,
on a VAX 7610 with DEMFA. We can't achieve that throughput, nor can Wollongong.
TGV's Multinet TCP/IP is claimed to reach 40Mbps using FFI, but I understood
that FFI was black magic/unsupported/undocumented and was going away with 5.5-2.
Is this the case?
If so,
- is VCI the replacement on 5.5-2 and higher?
- Where is VCI documented, please?
- Will TGV's Multinet crash on 5.5-2?
Customer refuses to pay for the 7610 till we can achieve stated objectives,
so any info would be *extremely* welcome.
Many thanks,
/Pete "just another poor field schmuck" Pinter
NIS Calgary
|
| 803.4 | | STAR::GAGNE | David Gagne - VMS/LAN Development | Wed Dec 09 1992 15:42 | 16 |
| As of VMS V5.5-2, there are no longer any users of FFI, so there are no
more test applications for it. If it still works is beyond me. It is
possible for a problem to exist in the FFI code and for VMS testing to
never find it because that interface is not exercised by any testing
done within VMS and possibly not at any of the Internal or External
sites.
The VCI will be publicly documented ASAP. I am working on the document
in my spare time and will ship it with a future release of VMS.
On ALPHA VMS, the FFI does not exist. When the ALPHA code is pulled
back into the VAX releases (and this is planned for a release already),
then the FFI code will no longer exist on VAX VMS.
Contact the UCX folks for some insight on their ability to get you the
performance you need.
|