DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Lukáš Šišmiš" <sismis@cesnet.cz>
Cc: dev@dpdk.org
Subject: Re: Outlook for DPDK multi-process support
Date: Wed, 8 Feb 2023 16:12:14 -0800	[thread overview]
Message-ID: <20230208161214.58fc929e@hermes.local> (raw)
In-Reply-To: <71e8deaf-82f0-407d-244b-322c40ad65ab@cesnet.cz>

On Wed, 8 Feb 2023 15:03:43 +0100
Lukáš Šišmiš <sismis@cesnet.cz> wrote:

> 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.

Impossible to predict the future, but until/unless something better is developed
there will be users.

> 
> 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.

The issue has been that some drivers and API's don't work with multi-process
support. If it is in the documentation for the configuration it should work
but like almost anything in software, until is implemented, tested, and maintained
there is no perfect way to tell.


      reply	other threads:[~2023-02-09  0:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 14:03 Lukáš Šišmiš
2023-02-09  0:12 ` Stephen Hemminger [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=20230208161214.58fc929e@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=sismis@cesnet.cz \
    /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).