Home
QNX Software Development Platform
QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running the QNX OS 8.0.
OS Components & Operations
High-Performance Networking Stack (io-sock) User's Guide
This guide contains instructions for implementing and using the QNX OS High-Performance Networking Stack and its manager, io-sock.
Running io-sock with Diagnostic Features

QNX Momentics IDE User's Guide
This User's Guide describes version 8.0 of the Integrated Development Environment (IDE) that's part of the QNX Tool Suite.
QNX Software Development Platform
QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running the QNX OS 8.0.
- Quickstart Guide
- System Architecture
  The System Architecture guide accompanies the QNX OS and is intended for both application developers and end-users.
- OS Components & Operations
  - Boot Optimization Guide
    The Boot Optimization Guide describes techniques you can use to reduce the time from your board's initial power on until you have a fully functional QNX system running on the board.
  - Building Embedded Systems
    The Building Embedded Systems guide is intended for developers who are developing or building BSPs for QNX OS embedded systems.
  - Customizing a BSP
    While QNX provides Board Support Packages (BSPs) for many common platforms and their individual variants, in some cases, you need a BSP for a board that QNX does not provide. If this is the case, you can modify a QNX BSP or develop your own.
  - Device Publishers Developer's Guide
  - High Availability Framework Developer's Guide
  - High-Performance Networking Stack (io-sock) User's Guide
    This guide contains instructions for implementing and using the QNX OS High-Performance Networking Stack and its manager, io-sock.
    - Overview
    - Privilege Control
      Like other components that run on QNX OS, the privileged operations required by io-sock and networking components are protected by process manager abilities. These abilities are configured either directly by the components themselves, or, preferably, via security policies that are defined by the system integrator.
    - Packet Filtering
    - Starting io-sock and Driver Management
    - Running io-sock with Diagnostic Features
    - Networking Services
      The io-sock networking stack provides services ported from FreeBSD.
    - Protocols
      The io-sock networking stack provides Internet protocols ported from FreeBSD.
    - Networking APIs
    - Networking Utilities
    - Writing Network Drivers for io-sock
    - A Hardware-Independent Sample Driver
    - Adding PTP to io-sock Network Drivers
      This appendix describes how to add 2-Step Precision Time Protocol (PTP) Ethernet packet timestamping functionality to an io-sock driver.
    - PTP Module Library API
      These PTP module functions are implemented by the PTP module. Networking drivers use them to handle actions such as transmit (Tx) and receive (Rx) timestamping and handing off PTP I/O-command (ioctl()) command processing.
  - PCI Server User's Guide
  - Performance Tuning User's Guide
  - SMMUMAN User's Guide
  - System Analysis Toolkit (SAT) User's Guide
  - Technotes
  - User's Guide
    The QNX OS User's Guide is intended for all users of a QNX OS system, from system administrators to end users.
- Graphics
- Programming
- System Security Guide
  The QNX System Security Guide is intended for both system integrators who are responsible for the security of a QNX OS system and developers who want to create a QNX OS resource manager free from vulnerabilities.
- Utilities & Libraries
- Migrating to QNX OS 8.0
QNX Software in the Cloud
QNX Toolkit for Visual Studio Code
This User's Guide describes the QNX^® Toolkit for Visual Studio Code. The guide introduces you to the QNX Toolkit by explaining the QNX development environment and how to build, run, and debug your QNX^® Operating System (OS) applications and systems.
Typographical Conventions, Support, and Licensing
This section describes the typographical conventions used throughout the documentation, explains how to obtain technical support, and provides some information about licensing.

Running io-sock with Diagnostic Features

QNX SDP8.0High-Performance Networking Stack (io-sock) User's GuideAPIArchitecture

The io-sock network stack, networking drivers, and modules are also provided in diagnostic versions. They have the same name as the standard version with a -diag suffix: io-sock-diag, devs-em-diag.so, and so on.

Use the diagnostic versions of the binaries when you are developing a new io-sock driver or module. They include extra checks and some useful macros and functions are only enabled in the diagnostic versions (e.g., KASSERT, mtx_assert). Because they use significantly more system resources than the standard versions, you shouldn't use them during performance testing or in production systems.

Specifying the diagnostic stack and drivers

When you use the diagnostic versions of io-sock or networking drivers, you also must use diagnostic versions of the driver or stack because the added checks require extra information that is passed between stack and driver.

When you specify a driver with the io-sock-diag command, the appropriate diagnostic driver is loaded automatically. For example, the following command loads devs-em-diag.so:

io-sock-diag -m pci -d em

The diagnostic driver is also automatically loaded when you load a driver using mount and specify the driver using its short name. For example, if io-sock-diag is running, the following command loads devs-em-diag.so (assuming the driver for PCI bus devices was started earlier):

mount -T io-sock em

But if you run io-sock-diag and specify the full name of the driver, make sure you specify the diagnostic driver. For example:

mount -T io-sock /lib/dll/devs-em-diag.so

Writing diagnostic network drivers

For diagnostic versions of io-sock network drivers, the following defines are set automatically by the devs.mk file (which is included by the network driver recursive makefile):

CCFLAGS+= -DINVARIANTS -DINVARIANT_SUPPORT -DKTR

Running io-sock-diag in the foreground

Specify -o foreground with io-sock-diag to stop io-sock from becoming a daemon. This option is valid only with io-sock-diag. As with standard io-sock, all logs are sent to slogger2. You can use -o foreground in combination with the DL_DEBUG environment variable to debug library loading issues.

Page updated: August 09, 2024