In order to maximize performance of the Open vSwitch DPDK datapath, it pre-allocates hugepage memory. As a user you are responsible for telling Open vSwitch how much hugepage memory to pre-allocate. The question of exactly what value to use often arises. The answer is, it depends.
There is no simple answer as it depends on things like the MTU size of the ports, the MTU differences between ports, and whether those ports are on the same NUMA node. Just to complicate things a bit more, there are multiple overheads, and alignment and rounding need to be accounted for at various places in OVS-DPDK. Everything clear? OK, you can stop reading then!
However, if not, read on.
Continue reading “Open vSwitch-DPDK: How Much Hugepage Memory?”
I work at Red Hat on GCC, the GNU Compiler Collection.
My main focus for the last year has been on making GCC easier to use, so I thought I’d write about some of the C and C++ improvements I’ve made that are in the next major release of GCC, GCC 8. You can easily install GCC 8 on Red Hat Enterprise Linux 6 and 7 using Red Hat Developer Toolset (DTS). GCC 8 is the default compiler in Red Hat Enterprise Linux 8 Beta. GCC 8 is also available in Fedora 28 and later.
Continue reading “Usability improvements in GCC 8”
Compiled files, often called binaries, are a mainstay of modern computer systems. But it is often hard for system builders and users to find out more than just very basic information about these files. The Annobin project exists as means to answer questions like:
- How was this binary built?
- What testing was performed on the binary?
- What sources were used to make the binary ?
The Annobin project is an implementation of the Watermark specification , which details how to record extra information in a binary. One important feature of this specification is that it includes an address range for the information stored. This makes it possible to record the fact that part of a binary was compiled with one set of options and another part was recorded with a different set of options.
Continue reading “Annobin – Storing Extra Information in Binaries”
Red Hat Container Development Kit (CDK) provides a Container Development Environment (CDE) that allows users to build a virtualized environment for OpenShift. This environment is similar to the user’s production environment and does not need other hardware or a physical cluster. CDK is designed to work on a single user’s desktop computer.
Continue reading “Running CDK 3.0 on Fedora 25”
Why use RPMs (distribution packages in general) at all ?!
Distribution RPMs enables you to get signed curated content, with security updates, bug fixes, general updates, some level of testing, and known ways of reproducing the build locally. Of course, it has its cost mostly in the package size overhead and packaging infrastructure overhead (yum, dnf, apt….).
Continue reading “Basics of Go in Fedora”
In 2016, many improvements happened in the ABI static analysis framework that is Libabigail. In this article we’ll present how fedabipkgdiff, a new Libabigail tool can help Fedora users, developers and others to analyze ABI changes of libraries carried by packages of the distribution.
Continue reading “ABI change analysis of Fedora packages”
Fedora users seeking help on installing Container Development Kit (CDK), here is how you can install CDK 2.2 on your Fedora 24. These same steps can be used for CDK 2.3 too.
CDK provides a container development environment, to build production-grade applications, for use on OpenShift.
The installation of CDK 2.2 on Fedora essentially involves the following stages:
Setting up your virtualization environment
You need to first install the virtualization software, in this case, KVM/libvirt, and then proceed to install Vagrant and its additional plugins to enable the various features of CDK.
Continue reading “Installing Red Hat Container Development Kit on Fedora”
The Internet of Things is a very new “thing” to us, but when we think of it, we’ve had access to the internet for a long period of time. We use “things” in day to day life that have been making our life easier for as long as we can remember.
Let’s take a common light bulb as an example. It consumes energy and produces light, which helps us everyday. Technology improvements have stripped down the consumption of resources to a bare minimum, while at the same time optimizing the output; efficiency and function has gone up. We even have internet connected and controllable light bulbs that change colors, operate on timers, and cooperate via mesh networks.
We live in an era where the mobile and telecommunications industries are booming, and the speed of internet would have been un-imaginable just one decade years before. Hence, the idea of making things smarter by connecting them to the internet, analyzing petabytes of historical and real-time data, and automating their operation becomes more and more a reality. This will result in a smarter way of living, since IoT affects almost all the major areas of the industry: Agriculture, Healthcare, Home Automation, and many more.
This post is a proof of concept of how easy it is to smartly control lights on an Arduino without ethernet shield, but rather over HTTP. The idea is to let you control a single light or series of lights in your house with just a tap of an application (with a proper internet connection of course.)
Continue reading “Smart light with Arduino in Fedora / RHEL”
Before and after Fedora releases, there are updates that keep coming in to fix bugs or add minor features to packages included in Fedora. To ensure that these are stable and don’t affect the performance of the existing system, we do “update testing”. Once testing is complete, we share our results and make sure that the developer is aware about the bugs and the success rate of the package. This article will explain how to participate in update testing and contribute to a high quality Fedora release!
(Editor’s note: Fedora is the upstream project for Red Hat Enterprise Linux (RHEL), which is now free for development use.)
Continue reading “Fedora “update testing” with Bodhi”
Release validation testing is a process which takes place before the official Fedora release. (Fedora is the upstream, community project from which RHEL is built.) Before the Final (GA) release, we have Alpha and Beta pre-releases and at each of these milestones, nightly builds (nightlies) and composes are released and tested to ensure that the release meets quality standards. Release validation testing is one way you can help Fedora get better, and this post will talk about how you can start off from scratch.
Continue reading “Getting Started with Release Validation Testing in Fedora QA”