-
Notifications
You must be signed in to change notification settings - Fork 8
ntttcp: Adding build files #147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
-DCMAKE_INSTALL_PREFIX="$(PREFIX)" \ | ||
-DCMAKE_STAGING_PREFIX="$(INSTALL_ROOT)/$(CPUVARDIR)/$(PREFIX)" \ | ||
-DCMAKE_MODULE_PATH="$(CMAKE_MODULE_PATH)" \ | ||
-DCMAKE_INSTALL_INCLUDEDIR="$(INSTALL_ROOT)/$(PREFIX)/include" \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You might have relocation issues if CMAKE_INSTALL_INCLUDEDIR is not relative to CMAKE_INSTALL_PREFIX and CMAKE_STAGING_PREFIX. See #132
source ~/qnx/800/qnxsdp-env.sh | ||
fi | ||
cd ~/workspace | ||
BUILD_TESTING="ON" QNX_PROJECT_ROOT="$(pwd)/ntttcp-for-linux/src" make -C build-files/ports/ntttcp install |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to have an iosock job and an iopkt job?
# Build ntttcp-for-linux | ||
BUILD_TESTING="ON" QNX_PROJECT_ROOT="$(pwd)/ntttcp-for-linux/src" make -C build-files/ports/ntttcp install -j4 | ||
|
||
**NOTE**: for building 710 use io-sock library for socket. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is still in the code block - add # for comments
# Build ntttcp-for-linux | ||
BUILD_TESTING="ON" QNX_PROJECT_ROOT="$(pwd)/ntttcp-for-linux/src" make -C build-files/ports/ntttcp install -j4 | ||
|
||
**NOTE**: for building 710 use io-sock library for socket. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment via # as we are still in the code block
BUILD_TESTING="ON" QNX_PROJECT_ROOT="$(pwd)/ntttcp-for-linux/src" make -C build-files/ports/ntttcp install -j4 | ||
|
||
**NOTE**: for building 710 use io-sock library for socket. | ||
download io-sock from http://anvil-server-n1.bts.rim.net/client/index.html#/packageDetails/com.qnx.qnx710.target.net.iosock/0.0.2.00622T202102120033S |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this packaged and available in QNX software centre? Might be easier to recommend installation from there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.rim.net is internal. io-sock needs to come from QSC.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you want to add an inline command it might be easiest to use qnxsoftware_clt
NTTTCP is a multi-threaded Linux network throughput benchmark tool.
While we are successfully able to measure network throughput, retrieving detailed system metrics has proven more challenging due to differences between Linux and QNX.
On Linux, we rely on system files such as /proc/net/netstat, /proc/interrupts, and /proc/cpuinfo to gather CPU and interrupt-related statistics. These interfaces are not available on QNX.
For QNX, we plan to explore accessing system-level data via the syspage interface, which may allow us to retrieve similar information (e.g., CPU topology, interrupts).
Reference: https://www.qnx.com/developers/docs/7.1/index.html#com.qnx.doc.neutrino.lib_ref/topic/s/syspage_entry.html).
Since throughput measurement is our primary objective and is already working, we will defer the remaining system-level metric integration to a later phase.