From: Ray Kinsella <mdr@ashroe.eu>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-announce] Accepted talks in FOSDEM 2020
Date: Fri, 20 Dec 2019 11:15:09 +0000 [thread overview]
Message-ID: <892b48d4-9edd-eb33-e431-8192f4acb522@ashroe.eu> (raw)
In-Reply-To: <2070170.Jc5xOWi4kn@xps>
+1, it is going to be _fabulous_
Ray K
On 20/12/2019 11:13, Thomas Monjalon wrote:
> The comittee for SDN devroom at FOSDEM is pleased to announce
> the schedule is available.
>
> Six talks mentioning DPDK are accepted:
>
> - Fundamental Technologies We Need to Work on for Cloud-Native Networking
> https://fosdem.org/2020/schedule/event/fundamental_technologies_we_need_to_work_on_for_cloud_native_networking/
>
> - Skydive - A real time network topology and protocols analyzer
> https://fosdem.org/2020/schedule/event/real_time_network_topology_and_protocols_analyzer/
>
> - Do you really see what’s happening on your NFV infrastructure?
> https://fosdem.org/2020/schedule/event/do_you_really_see_whats_happening_on_your_nfv_infra/
>
> - Analyzing DPDK applications with eBPF
> https://fosdem.org/2020/schedule/event/analyzing_dpdk_applications_with_ebpf/
>
> - Mixing kool-aids! Accelerate the internet with AF_XDP & DPDK
> https://fosdem.org/2020/schedule/event/mixing_kool_aids/
>
> - Dial your Networking Code up to 11
> https://fosdem.org/2020/schedule/event/dial_your_networking_code_up_to_11/
>
> You will probably be interested by the other talks of the track:
> https://fosdem.org/2020/schedule/track/software_defined_networking/
>
> FOSDEM welcomes a large number of devrooms during two days (Feb 1-2),
> allowing to learn, meet and discuss about a lot of topics.
> See you there!
>
>
prev parent reply other threads:[~2019-12-20 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 11:13 Thomas Monjalon
2019-12-20 11:15 ` Ray Kinsella [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=892b48d4-9edd-eb33-e431-8192f4acb522@ashroe.eu \
--to=mdr@ashroe.eu \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).