Browse Prior Art Database

Communications Transmit Buffer Serial Utilization

IP.com Disclosure Number: IPCOM000034576D
Original Publication Date: 1989-Mar-01
Included in the Prior Art Database: 2005-Jan-27
Document File: 1 page(s) / 11K

Publishing Venue

IBM

Related People

Lucas, JC: AUTHOR

Abstract

Disclosed is a method, interfacing with IBM Operating System/2 Extended Edition - Asynchronous Communications Device Interface, which provides automatic pacing of transmit data. The interfacing application is well behaved and capable of operating in a multi-tasking environment. A serialization semaphore is employed to control multi-thread access to the Asynchronous Communications Device Interface transmit buffer. The application's main thread adds data to this transmit buffer under the control of this serialization semaphore. A separate execution thread is used to issue the Asynchronous Communication Device Interface transmit requests, also under the control of this serialization semaphore.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 100% of the total text.

Page 1 of 1

Communications Transmit Buffer Serial Utilization

Disclosed is a method, interfacing with IBM Operating System/2 Extended Edition - Asynchronous Communications Device Interface, which provides automatic pacing of transmit data. The interfacing application is well behaved and capable of operating in a multi-tasking environment. A serialization semaphore is employed to control multi-thread access to the Asynchronous Communications Device Interface transmit buffer. The application's main thread adds data to this transmit buffer under the control of this serialization semaphore. A separate execution thread is used to issue the Asynchronous Communication Device Interface transmit requests, also under the control of this serialization semaphore. The free space management capability of Asynchronous Communications Device Interface causes the thread, with a transmit request, to be blocked when the transmit buffer-free space falls below a threshold. This thread, in turn, keeps the serialization semaphore and will cause the main thread execution to be suspended until the semaphore is freed. The application will execute a sufficient amount of time to keep the transmit buffer filled, thus causing a constant transmission of data. This provides pacing control with minimum overhead to the application.

1