From: Stephen Hemminger <stephen@networkplumber.org>
To: Shyam Shrivastav <shrivastav.shyam@gmail.com>
Cc: Cristofer Martins <CristoferMartins@hotmail.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] General Questions
Date: Thu, 9 Apr 2020 08:32:36 -0700 [thread overview]
Message-ID: <20200409083236.08573753@hermes.lan> (raw)
In-Reply-To: <CAGSp03=E6oj=BDTvN-9BeUvBcKeLMQQLwqJxNBMDXrZoKq5qZw@mail.gmail.com>
On Thu, 9 Apr 2020 20:57:19 +0530
Shyam Shrivastav <shrivastav.shyam@gmail.com> wrote:
> From my experience as dpdk user
>
> On Thu, Apr 9, 2020 at 11:41 AM Cristofer Martins <
> CristoferMartins@hotmail.com> wrote:
>
> > Well the reason i thought about using dpdk(together with a user space tcp
> > stack) is because my tcp code spend so much time with syscalls that
> > removing that would allow better throughput and latency. Is this a valid
> > reason? My software runs in single core(and most of time in cheap vps) so i
> > want to extract the best i can from them.
> >
>
> Yes using dpdk instead of getting packets from kernel stack increases
> performance
>
>
>
> > The other question is, can dpdk runs alongside with the linux network
> > stack? I want to use dpdk in my special app but i still want to have ssh
> > and apps working as expected without any modification.
> >
> Interface used by dpdk is not available, at least another interface
> required for management/access & other network apps
>
>
>
> >
> > Thanks in advance.
> >
This might be a good use case for AF_XDP with or without DPDK
next prev parent reply other threads:[~2020-04-09 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 6:11 Cristofer Martins
2020-04-09 14:58 ` Stephen Hemminger
2020-04-09 15:27 ` Shyam Shrivastav
2020-04-09 15:32 ` Stephen Hemminger [this message]
2020-04-09 20:58 ` Thomas Monjalon
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=20200409083236.08573753@hermes.lan \
--to=stephen@networkplumber.org \
--cc=CristoferMartins@hotmail.com \
--cc=shrivastav.shyam@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).