From: Ankit Aggarwal <ankit.a@irage.in>
To: Andrew Rybchenko <arybchenko@solarflare.com>, users@dpdk.org
Cc: dev@dpdk.org
Subject: Re: [dpdk-users] [dpdk-dev] Solarflare DPDK
Date: Tue, 21 Mar 2017 14:35:33 +0530 [thread overview]
Message-ID: <CACCUyHu_57FORwfPStstshbC0_ihU-7e4gunucaZnTHHxOAqPw@mail.gmail.com> (raw)
In-Reply-To: <ed4265a7-db51-5b68-0598-fcd77f22e219@solarflare.com>
Hi Andrew
I'm developing a kit for kernel bypass purpose.OpenOnLoad already provides
a way to do kernel bypass.
Can dpdk also be used for kernel bypassing purpose on intel/solarflare
cards?
Ankit Aggarwal
On Tue, Mar 21, 2017 at 1:48 PM, Andrew Rybchenko <arybchenko@solarflare.com
> wrote:
> Hi Ankit,
>
> (May be users@dpdk.org is a better place for such questions)
>
> OpenOnload provides a user-level TCP/IP stack with POSIX interface –
> transparently runs any Linux sockets binary without requiring any changes
> to the application. "DPDK is a set of libraries and drivers for fast
> packet processing. [snip] DPDK is not a networking stack" (quotes from
> dpdk.org). So they have very different end use-cases.
>
> So if end-use case is performing packet processing and/or switching
> packets between network interfaces then DPDK allows an open API to be used.
> However, if app needs to terminate TCP or UDP flows then OpenOnload
> provides a mature TCP/IP stack. We’ve seen good results with applications
> such as Nginx with OpenOnload.
>
> Regards,
> Andrew.
>
>
> On 03/20/2017 05:22 PM, Ankit Aggarwal wrote:
>
> Hi DPDK Users/devs
>
> Can you please tell me the benefits of using DPDK over openonload for
> solarflare cards?
>
> Ankit Aggarwal
>
>
>
next parent reply other threads:[~2017-03-21 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACCUyHuiuhc8sbzcdACSwOApp3hKyGMh92Lh7tTR+fOJRPg8sg@mail.gmail.com>
[not found] ` <ed4265a7-db51-5b68-0598-fcd77f22e219@solarflare.com>
2017-03-21 9:05 ` Ankit Aggarwal [this message]
2017-03-21 9:30 ` Anupam Kapoor
2017-03-21 9:48 ` Ankit Aggarwal
2017-03-21 10:22 ` Anupam Kapoor
2017-03-21 13:30 ` Andrew Rybchenko
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=CACCUyHu_57FORwfPStstshbC0_ihU-7e4gunucaZnTHHxOAqPw@mail.gmail.com \
--to=ankit.a@irage.in \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--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).