Email: firstname.lastname@example.org • Twitter: @benhutchingsuk • Debian: benh • Gitweb: git.decadent.org.uk • Github: github.com/bwhacks
Speaker: Peter Zijlstra
LWN article: https://lwn.net/Articles/799454/
This was about restricting which tasks share a core on CPUs with SMT/hyperthreading. There is current interest in doing this as a mitigation for speculation leaks, instead of disabling SMT altogether.
SMT also makes single-thread processing speed quite unpredictable, which is bad for RT, so it would be useful to prevent scheduling any other tasks on the same core as an RT task.
Speakers: Jim Hull and Betty Dall of HPE
Connections are point-to-point between "components". Switch components provide fan-out.
Components can be subdivided into "resources" and also have "interfaces".
No requirement for a single root (like typical PCIe) and there can be redundant connections forming a mesh.
Fabric can span multiple logical computers (OS instances). Fabric manager assigns components and resources to them, and configures routing.
Protocol is reliable; all writes are acknowledged (by default). However it is not ordered by default.
Components have single control space (like config space?) and single data space (up to 2⁶⁴ bytes). Control space has a fixed header and then additional structures for optional and per-interface registers.
Each component has 12-bit component ID (CID) which may be combined with 16-bit subnet ID (SID) for 28-bit global component ID (GCID).
Coherence is managed by software.
Bridge from CPU to Gen-Z needs MMUs to map between local physical address space and fabric address space. Normally also has DMA engines ("data movers") that can send and receive all types of Gen-Z packets and not just read/write. These bridges are configured by the local OS instance, not the fabric manager.
Should behave similarly to PCI and USB, so far as possible. Leave policy to user-space. Deal with the fact that most features are optional.
The Gen-Z subsystem needs to provide APIs for tracking PASIDs in IOMMU and ZMMU. Similar requirements in PCIe; should this be generic?
How can Gen-Z device memories be mapped with huge pages?
Undecided whether a generic kernel API for data movers is desirable. This would help kernel I/O drivers but not user-space I/O (like RDMA).
Interrupts work very differently from MSI. Bridge may generate interrupts for explicit interrupt packets, data mover completions, and Unsolicited Event Packets (link change, hotplug, …).
All nodes run local management services. On Linux these will be in user-space (LLaMaS).
(This means LLaMaS will need to be included in the initramfs if the boot device is attached through Gen-Z.)
Manager will use netlink to announce when resource has been assigned to the local node. Kernel then creates kernel device for it.
Moderator: Joe Lawrence
Speaker: Dmitry Vyukov
Dmitry outlined how the current kernel development processes are failing:
It takes a long time for new developers to become productive, or for developers to contribute to unfamiliar subsystems.
(None of this was new to me, but spelling out all these issues definitely had an impact.)
He advocates more consolidation and consistency, so that:
There was further discussion of this at the Kernel Maintainer Summit, reported in https://lwn.net/Articles/799134/.