From: Pavel Vazharov <freakpv@gmail.com>
To: users <users@dpdk.org>
Subject: Split traffic between the Linux stack and DPDK application
Date: Mon, 29 Jan 2024 18:09:28 +0200 [thread overview]
Message-ID: <CAK9EM193mhFEHNZgV86G59Zg0dRtViRLN=q097MocX0ZN-NeUA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 612 bytes --]
Hi there,
A DPDK can run on top of XDP sockets and use custom XDP program to split
the traffic between the Linux stack and the DPDK application. This way
still allows zero copy between the kernel and the DPDK application.
Is there another zero-copy way to achieve redirecting some part of the
traffic to the Linux kernel and another to a DPDK application?
For example, AFAIK I can run the DPDK application and redirect packets from
inside to the Linux stack via the DPDK KNI functionality but it'll be much
slower because it'll require packets copying and context switch (if I'm not
mistaken).
Regards,
Pavel.
[-- Attachment #2: Type: text/html, Size: 715 bytes --]
next reply other threads:[~2024-01-29 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 16:09 Pavel Vazharov [this message]
2024-01-29 17:21 ` 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='CAK9EM193mhFEHNZgV86G59Zg0dRtViRLN=q097MocX0ZN-NeUA@mail.gmail.com' \
--to=freakpv@gmail.com \
--cc=users@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).