GIT is a version control system that is used for software development and other version control tasks. As a distributed revision control system it is aimed at speed, data integrity, and support for

 [[likely]] and [[unlikely]]  Calendars & Timezones  std::span  Feature Test Macros  <version>  Immediate Functions – consteval  constinit  Class Enums and using Directive  Text Formatting all C++ headers are “importable”, e.g.  import <version>;  Everything in <version> is exported, including macros  Improves build throughput; <version> will be processed only once  Comparable to precompiled { for (int i { startValue }; i < startValue + numberOfValues; ++i) { time_t t { system_clock::to_time_t(system_clock::now()) }; cout << std::ctime(&t); co_yield i; } } int main() { auto

leap_seconds (https://youtu.be/WX3OmVu4lAs) • time_zone and time_zone_link (https://youtu.be/MODhhr7m-5s) • system_clock::now(), file_clock, leap second awareness (https://youtu.be/c7DT28TV0AY)9 Part II: Calendrical requirements.20 C++20’s chrono adds several new clocks ([time.clock]) Existing clocks (pre-C++20) • system_clock • (file_clock) New clocks (in C++20) • utc_clock • tai_clock • gps_clock • (file_clock)21 (file_clock)21 C++20’s chrono adds several new clocks ([time.clock]) Existing clocks (pre-C++20) • system_clock • (file_clock) New clocks (in C++20) • utc_clock • tai_clock • gps_clock • (file_clock)22 Why

and when work should happen … including some standard ones: an event loop, portable access to the system execution context, nursery for spawned work4 P2300: STD::EXECUTION Proposes: • A set of concepts done_as_error(sender, error) → sender … commutes the done signal into an error.19 SENDER/RECEIVER CONTROL FLOW20 BASIC LIFETIME OF AN ASYNC OPERATION SCHEDULER schedule SENDER Implementation details STRUCTURED PROGRAMMING Structured control flow constructs have a single entry and a single exit, permitting them to be treated like a black box. goto is an unstructured control flow construct conditional

PCI-Express bus.” -- https://developer.nvidia.com/blog/unified-memory-in-cuda- 6/ CPU vs GPU Memory System Memory GPU Memory 12 |“Unified Memory creates a pool of managed memory that is shared between is that the system automatically migrates data allocated in Unified Memory between host and device...” -- https://developer.nvidia.com/blog/unified-memory-in-cuda-6/ Unified Memory System Memory GPU is that the system automatically migrates data allocated in Unified Memory between host and device….” -- https://developer.nvidia.com/blog/unified-memory-in-cuda-6/ Unified Memory System Memory GPU

shared_ptr s1: control_block: atomic ref_count = 1; … control_block* ctrl; T12 Daniel Anderson -- danielanderson.net std::shared_ptr (the basics) T* ptr; shared_ptr s1: control_block: control_block* shared_ptr s2: control_block* ctrl; atomic ref_count = 2; …13 Daniel Anderson -- danielanderson.net std::shared_ptr (the basics) control_block: T T* ptr; control_block* ctrl; atomic … shared_ptr s2:14 Daniel Anderson -- danielanderson.net std::shared_ptr (the basics) control_block: T atomic ref_count = 0; …15 Daniel Anderson -- danielanderson.net std::atomic16

traffic ● Authorize in mesh traffic ● Summary #IstioCon Istio Architecture Connect, secure, control, and observe services. #IstioCon Security Architecture #IstioCon Bookinfo architecture without istio.io/v1beta1“ kind: "RequestAuthentication“ metadata: name: "jwt-example“ namespace: istio-system spec: selector: matchLabels: istio: ingressgateway jwtRules: - issuer: testing@secure security.istio.io/v1beta1 kind: AuthorizationPolicy metadata: name: require-jwt namespace: istio-system spec: action: ALLOW rules: - from: - source: requestPrincipals: ["testing@secure

Preview 5 Preview 6 Version 16.8 Preview 1 Preview 2 Preview 3 Preview 4 Preview 5 Version 16.9 Preview 1 Preview 2 Preview 3 Preview 4 Version 16.10 Preview 1 Preview 2 Preview 3 Version 16.11 CppCon development 4. Developer and Team Productivity At CppCon last year Announcing In Visual Studio 2019 version 16.11, C++20 is now feature complete • All features under /std:c++20 switch are production ready libraries available for installation • Built from source, on-demand • Centralized, tested catalog (no version conflicts) • Popular build targets supported by default, and you can add your own custom targets

with SELinux, AppArmor, Seccomp, cgroup VM-based Sandbox Kata-container BareMetal Only Heavy control logic Application kernel based Sandbox gVisor Compatibility problem, Bottleneck in sentry mVMd • Google implements the first Rust-based light VMM called CrosVM which is in Fuchsia operating system • AWS develops his own light VMM called Firecracker which is based of CrosVM • There are lots acpi linux-loader kvm-ioctls vm-virtio vsock net VFIO APIC vhost Cloud Hypervisor KVM File System Device Driver Host Linux Kernel vCPU block Memory Guest VM containerd + Kata-runtime create

microbenchmarking. • 2020: One user: High frequency of retiring objects. Unsharded list grew out of control. • 2020: Sharded cohorts without reclamation under lock. Fast. Scalable. Robust. Quasi-Synchronous com/facebook/folly under folly/synchronization/Hazptr.h  Working Draft, Extensions to C++ for Concurrency Version 2 (wg21.link/n4895).  Hazard Pointers: Safe Memory Reclamation for Lock-Free Objects, IEEE Transactions Hazard Pointers – Maged Michael Watch CPPCON 2021 Talk on Concurrency TS2 The Upcoming Concurrency TS Version 2 for Low-Latency and Lockless Synchronization (with Paul McKenney and Michael Wong)