DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Thomas Monjalon <thomas@monjalon.net>, announce@dpdk.org
Cc: dev <dev@dpdk.org>
Subject: Re: DPDK Summit Montreal - Schedule
Date: Thu, 5 Sep 2024 10:28:24 +0100	[thread overview]
Message-ID: <3041d897-02ea-4952-ae6f-e4e616ee21b7@amd.com> (raw)
In-Reply-To: <1995178.jZfb76A358@thomas>

On 8/13/2024 7:13 PM, Thomas Monjalon wrote:
> The next DPDK Summit will be hosted in Montreal, Canada on September 24-25.
> 
> 
> We will talk about the future of DPDK, the best userland networking libraries
> having an incredible hardware support from our large community.
> It will be an opportunity to connect, learn and collaborate with developers
> from around the world who contribute to and utilize DPDK.
> 
> Talks will cover CPU optimizations, GPU processing, machine learning,
> hashing, packet offload, cryptography, testing and more.
> 
> The schedule can be found here, almost complete:
> https://events.linuxfoundation.org/dpdk-summit/program/schedule/
> 
> 
> A workshop session is planned to allow debating and making progress
> in smaller group discussions about specific topics to be determined.
> Examples of such topics could be:
> 	- debuggability
> 	- power management techniques & efficiency
> 	- config restore bypass in ethdev port start
> 	- secondary process usage and limitations
> 
> Feel free to propose your ideas in advance so we can come prepared.
> Then we will organize ourselves in discussion groups
> in order to progress and hopefully reach some new conclusions.
> 

What do you think about 'rte_flow', it is a powerful tool but complex
and not adopted in same level by all vendors. As it hard to test, we are
having difficulty to provide consistency between vendor implementations.
We can discuss how to spread understanding among various vendors and
users, how to increase adoption, and future targets/plans.


Another one can be 'tooling', as a result of kernel bypass, some known
Linux networking tools does not work with DPDK solutions, and this
creates confusing and entry barrier for some people, this problem
mentioned a few times before.
Perhaps we should address this problem in a more structured way, to
design and later implement gradually some solutions. We can discuss
methods and plans to improve our tooling support.


Thanks,
ferruh

  reply	other threads:[~2024-09-05  9:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-13 18:13 Thomas Monjalon
2024-09-05  9:28 ` Ferruh Yigit [this message]
2024-09-06 14:09   ` Konstantin Ananyev
2024-09-06 19:32     ` Ferruh Yigit

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=3041d897-02ea-4952-ae6f-e4e616ee21b7@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=announce@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).