Conference planning document

Title: "XDP hands-on tutorial" Subject: [Indico] Abstract Acceptance notification (#48)

[2019-02-04 Mon 12:33] https://lists.netdevconf.org/pipermail/people/20190318/000275.html https://github.com/xdp-project/xdp-tutorial/releases/tag/2019-03-18-netdev0x13

Overall plan in conference/NetDevConf2019-0x13/tutorial_notes.html

We need a github repo that are easier to build than prototype-kernel github repo, as it requires the kernel source tree to build. The hands-on tutorial need to have an easier and more confined build-environment.

Started repo here: https://github.com/xdp-project/xdp-tutorial/

Related: How do we ensure participants can successfully run XDP at the event?

E.g.:

• Use metadata field for carrying per-packet data
• Don't replicate kernel state
• How to handle multiple programs on one interface

Question is if we need a real presentation for the XDP-tutorial, or if the GitHub READMEs are enough?

Summary after meeting (with Toke): Yes we will need a presentation: But mostly as a 10 minute intro.

Afterwards the presenters laptop can open the README files, as this will show what is the current exercise. And we want people to open these README.org files themselves, either via GitHub-webpage or in emacs.

The presentation will be placed in: xdp-project git-repo.

The reason behind not placing it in: xdp-tutorial git-repo, is that we want to evolve the xdp-tutorial without tying it to a specific conference. We will create a git-tag (or branch) that correspond to the conference presentation, to allow people link the two.

Brainstorm over topics in presentation:

• Initial slides.
• Reference to vikings
• Cover global readme
• About the veth-testlab setup
  • required kernel version
• Offer to help people with their own use-cases