linux-kernel - [ANNOUNCE] CFP: CPU Isolation Microconference

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:   Fri, 13 May 2022 16:21:43 +0200
From:   Juri Lelli <juri.lelli@...hat.com>
To:     LKML <linux-kernel@...r.kernel.org>
Cc:     Ingo Molnar <mingo@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Mel Gorman <mgorman@...e.de>,
        Vincent Guittot <vincent.guittot@...aro.org>,
        Juri Lelli <juri.lelli@...hat.com>,
        Steven Rostedt <rostedt@...dmis.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Valentin Schneider <vschneid@...hat.com>,
        Qais Yousef <qais.yousef@....com>,
        Phil Auld <pauld@...hat.com>,
        "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
        "Joel Fernandes (Google)" <joel@...lfernandes.org>,
        Quentin Perret <qperret@...gle.com>,
        Dietmar Eggemann <dietmar.eggemann@....com>,
        Luca Abeni <luca.abeni@...tannapisa.it>,
        Morten Rasmussen <Morten.Rasmussen@....com>,
        Dhaval Giani <dhaval.giani@...cle.com>,
        Chris Hyser <chris.hyser@...cle.com>,
        Waiman Long <longman@...hat.com>,
        Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
        Mike Galbraith <efault@....de>,
        Davidlohr Bueso <dave@...olabs.net>,
        Ben Segall <bsegall@...gle.com>, Will Deacon <will@...nel.org>,
        Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
        patrick.bellasi@...bug.net,
        Daniel Lezcano <daniel.lezcano@...aro.org>,
        Rik van Riel <riel@...riel.com>,
        Hillf Danton <hdanton@...a.com>,
        Frederic Weisbecker <frederic@...nel.org>,
        Viresh Kumar <vireshk@...nel.org>,
        Paul Turner <pjt@...gle.com>,
        Dario Faggioli <raistlin@...ux.it>,
        Andi Kleen <ak@...ux.intel.com>, Scott Wood <swood@...hat.com>,
        Clark Williams <williams@...hat.com>,
        Daniel Wagner <wagi@...om.org>,
        Mark Brown <broonie@...nel.org>,
        Daniel Bristot de Oliveira <bristot@...hat.com>,
        Nicolas Saenz Julienne <nsaenzju@...hat.com>,
        Marcelo Tosatti <mtosatti@...hat.com>,
        Karl Rister <krister@...hat.com>,
        Andrew Theurer <atheurer@...hat.com>
Subject: [ANNOUNCE] CFP: CPU Isolation Microconference - Linux Plumbers
 Conference 2022

CPU Isolation can be considered as an holistic functionality that stems
from a close combination of several kernel and userspace components
working together to shield workloads with extreme latency or performance
requirements from interruptions (also known as Operating System noise).
An example of such type of workloads are DPDK (Data Plane Development
Kit) use cases (Telco/5G) where even the shortest interruption (e.g., a
few microseconds to service an IPI) can cause packet losses, eventually
leading to exceeding QoS requirements.

Despite considerable improvements in the last few years towards
implementing full CPU Isolation (nohz_full, rcu_nocb, isolcpus, etc.), a
certain amount of issues remain to be addressed, as it is still
relatively simple to highlight sources of OS noise just by running
synthetic workloads mimicking polling (always running) type of
application similar to the ones mentioned above.

Recently, improvements and discussions about CPU isolation features have
been made and discussed in LKML [1,2,3], and tools such as osnoise
tracer and rtla osnoise [4,5] improved the CPU isolation analysis.
Nevertheless, this is an ongoing process, and discussions are needed to
speed up solutions for existing discussions and improve the existing
tools and methods.

With this microconference we thus want to get together to discuss open
problems, most notably: how to improve the identification of OS noise
sources (expanding runtime tracing and/or code inspection tools), how to
track them publicly (repo/DB) and how to tackle the sources of noise
that have already been identified (e.g, [1,2,3]).

A non exhaustive list of potential topics is:

- OS noise profiling (format and public DB for the community)
- Tracing to detect OS noise: the rtla osnoise tracer and what it’s
  missing TLB/icache flush deferral [1]
- Extend cpuset v2 cpu partition feature to replace isolcpus kernel
  cmdline
- rt-trace-bpf tool
- Task isolation
- smp_call_function API improvements

If you are interested in participating in this microconference and have
topics to propose, please use the LPC CfP process [6], and select "CPU
Isolation MC" for the "Track".

The submission deadline is June 30.

Come and join us in the discussion, we hope to see you there!

In case of doubts, feel free to contact the MC Leads:

Juri Lelli <juri.lelli@...hat.com>
Daniel Bristot de Oliveira <bristot@...hat.com>

refs.
1 - https://lore.kernel.org/all/20210929151723.162004989@infradead.org/
2 - https://lore.kernel.org/lkml/20220315153132.717153751@fedora.localdomain/
3 - https://lore.kernel.org/lkml/20211103170512.2745765-1-nsaenzju@redhat.com/
4 - https://www.kernel.org/doc/html/latest/trace/osnoise-tracer.html
5 - https://www.kernel.org/doc/html/latest/tools/rtla/rtla-osnoise.html
6 - https://lpc.events/event/16/abstracts/