DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Lukáš Šišmiš" <sismis@cesnet.cz>
To: dev@dpdk.org
Subject: Outlook for DPDK multi-process support
Date: Wed, 8 Feb 2023 15:03:43 +0100	[thread overview]
Message-ID: <71e8deaf-82f0-407d-244b-322c40ad65ab@cesnet.cz> (raw)

Hello all,


I'd like to ask you about future outlook of multi-process support in 
DPDK (https://doc.dpdk.org/guides/prog_guide/multi_proc_support.html).

On DPDK Userspace 2022, I have presented a solution that uses 
multi-process support (https://youtu.be/TtiR74w3Yv4) in Suricata IDS.

But after the talk, some people have reached out to me and suggested 
that multi-process support might not be supported in the long-term.

As I would like to continue developing the concept further, I thought it 
might be a good idea to consult the idea and possibly open the discussion.


As an alternative solution to multi-process support I see either 
vhost-user/virtio/vDPA or VF. However, I couldn't find any performance 
benchmarks on this topic.

Further guidance is highly appreciated.

Thank you all in advance.


Best regards,

Lukas Sismis


             reply	other threads:[~2023-02-08 14:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 14:03 Lukáš Šišmiš [this message]
2023-02-09  0:12 ` Stephen Hemminger

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=71e8deaf-82f0-407d-244b-322c40ad65ab@cesnet.cz \
    --to=sismis@cesnet.cz \
    --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).