Samba had experimental support for multi-channel for quite a while. SMB3 has a few concepts to replay requests safely. We now implement them completely (and in parts better than a Windows Server). The talk will explain how we implemented the missing features. With the increasing amount of network throughput, we'll reach a point where a data copies are too much for a single cpu core to handle. This talk gives an overview about how the io_uring infrastructure of the Linux kernel could be used in order to avoid copying data, as well as spreading the load between cpu cores.

On the domain controller side we got a lot of updates recently: - Updated Heimdal - Working with the latest MIT Kerberos On the member server side we fixed some critical bugs and have plans for future improvements how a file server can avoid as much domain controller interaction as possible.

With the increasing amount of network throughput, we'll reach a point where a data copies are too much for a single cpu core to handle. This talk gives an overview about how the io_uring infrastructure of the Linux kernel could be used in order to avoid copying data, as well as spreading the load between cpu cores. A prototype for this exists for quite some time and shows excellent results.

Samba 4.20 will ship with rpcd_witness, which provides a service for MS-SWN within a ctdb cluster. This service can be used by a client in order to monitor cluster nodes and gives an administrator the chance to move specific connection to another node. The talk explains the current state, the design and some strange things a Windows client is doing.