Make gpib-enet devices in one front-end have different OIDs
On LEBIT1, at least, all the GPIB-ENET devices share one OID, which is not ideal. This makes reading one from one gpib-enet link wait on all others (at the OID semaphore level). This is (probably) currently causing large readback delays in LEBIT1 frontend.
- Determine if the driver supports multiple OIDs in the same front-end
- If not, make it so it does
- Then split the different gpib-enet links onto different OIDs.
#1 Updated by Richard Neswold about 2 years ago
- Status changed from New to Assigned
I don't know how the driver is organized, but if each enet box is communicated through a separate socket, the driver could be made thread-safe and then the OID semaphore can be removed. Not sure which approach is better for this driver. Depends upon how many global variables there are, I guess
#2 Updated by Jerry Firebaugh about 2 years ago
- Status changed from Assigned to Closed
Now support multiple (up to 8) OIDs. Convention I'm now following for device SSDN, is to give same OID for any device connected to a given enet box. However OID's can be assigned however like. A slow device could have it's own OID so that it does not hold up readings of other devices