| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
| |
This patch changes the probing logic to select the first available
dnbd3-server submitted by the ioctl OPEN call. All other specified
dnbd3-servers are added to the alternative server list and do not have
to be available.
|
|
|
|
|
|
|
|
|
|
| |
The ioctl OPEN call for DNBD3 devices exposed by the dnbd3 Linux kernel
module, is extended with a fixed array of dnbd3 hosts. The fixed array
allows the dnbd3-client to submit host information (IP address and port)
of multiple dnbd3-servers. This information is used to probe all
submitted dnbd3-servers and add them to the alternative dnbd3-server
list. If at least one dnbd3-server is not reachable, the OPEN ioctl call
will abort with an error code.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
saveLoadAllCacheMaps() is called frequently, and a 'full' run can take
some time. If we only update the nextSave timestamp when we're done, we
might already have a concurrent call to the function, which will also do
a 'full' run, since the timestamp is not updated yet. This doesn't break
anything, but leads to even more disk activity, which is probably
already high, given that the previous run is not done yet.
|
|
|
|
|
| |
This patch sets the programming languages of each CMake project to C. With
this change, CMake does not search for an unused C++ compiler anymore.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds the following CMake targets
- package
- source
to build bundeled packages. Those packages contain either all built
binary artifacts or all source files for source code distribution. Both
CMake targets are available in Release build configuration.
|
|
|
|
|
| |
The afl-fuzz support for the dnbd3-server requires an AFL C compiler
like afl-gcc and can be enabled with the CMake option DNBD3_SERVER_AFL.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This change restructures the source code directories, separates shared
form non-shared application code and adds CMake dependencies. These
dependencies allow the tracking of changes and trigger a rebuild of
those build targets where changed files are involved.
WARNING: Note that the support of the DNBD3_SERVER_AFL build option is
not supported yet. Thus, the option should be never turned on.
|
|
|
|
|
|
|
|
|
| |
This patch implements the old time structures to support Linux kernels
prior to version 5.1.x.
WARNING: This change to the deprecated time structures does not solve
the Y2038 issue. Thus, the dnbd3 Linux kernel module can only run under
Linux kernels prior to version 5.1.x until the end of year 2037.
|
|
|
|
|
|
|
|
|
|
| |
This patch replaces the deprecated kernel_setsockopt() function with the
socket generic function sock_setsockopt() to set the send and receive
timeout for all used sockets in the kernel module. The timeout data type
is choosen according to the available kernel version, so that the dnbd3
kernel module supports the new y2038-problem-solving socket options.
With both changes, the kernel module runs on Linux kernel 5.4 LTS and
later (including Linux kernel 5.9).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change converts all debug messages to support the Linux kernel's
dynamic debug feature. Debug messages can be enabled or disabled by
the debug feature if the
- kernel module is built in debug mode (EXTRA_CFLAGS=-g -DDEBUG)
- Linux kernel supports dynamic debug (CONFIG_DYNAMIC_DEBUG is set)
This patch removes outdated kernel compatibility macros (used for Linux
kernels in version 4.x) and cleans up the kernel module's code.
|
|
|
|
|
|
|
|
|
|
|
| |
This converts the dnbd3 kernel module driver to use the blk-mq
infrastructure, which allows the dnbd3 kernel module driver to be
compatible with Linux kernels in version 5.x or later. The conversion of
the implementation uses one hardware queue to preserve the existing
send/receive and load-balancing logic, but can be scaled up in the
future. In addition to that, time measurements in the implementation are
converted to ktime based accessors to replace the use of deprecated time
interfaces.
|
|
|
|
|
| |
There was a logic bug that would favor a remotely looked up image rid,
even if we already found a higher revision locally.
|
| |
|
|
|
|
|
|
| |
Greatly improves performance when reading from the local disk cache, and
additionally avoids having everything in the fs cache twice (disk view
and fuse view).
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Still needs some cleanup and optimizations, variable naming sucks,
comments, etc.
|
|\ |
|
| |
| |
| |
| | |
Entries in _images array might ne NULL
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Should have tested in "Release" mode I guess.
Seems we're at about 24x performance this way, so hooray.
|
| |
| |
| |
| |
| |
| |
| | |
This is about 16x as fast as before with the lookup table
for processing 4 bytes at a time and should work on any AMD64
CPU made in the last decade.
We still need an AltiVec implementation for G5 though.
|