DPDK usage discussions
 help / color / mirror / Atom feed
From: Anupam Kapoor <anupam.kapoor@gmail.com>
To: Ankit Aggarwal <ankit.a@irage.in>
Cc: Anupam Kapoor <anupam.kapoor@gmail.com>,
	Andrew Rybchenko <arybchenko@solarflare.com>,
	users@dpdk.org
Subject: Re: [dpdk-users] [dpdk-dev] Solarflare DPDK
Date: Tue, 21 Mar 2017 15:52:04 +0530	[thread overview]
Message-ID: <87bmsvgcab.fsf@gmail.com> (raw)
In-Reply-To: <CACCUyHtaHaa5M29YzASxYwBhi_BX86riFUjY=KbY6wjLDDT=Kw@mail.gmail.com>


,----[ ankit-agarwal ]
| "but, in terms of functionality"
|
| Can you elaborate on that?
`----
sure, think l2 handling sepcifically, arp, neighbor table management
etc. for l3 you need to manage routing etc. etc., from l4 onwards you
need to worry about protocol specific handling, and protocol states
which may or may not last application lifetimes etc. etc.

but, i am guessing, openload's offering is already battle-tested, and
provides sane sematics for stuff outlined above, both on virtualized,
and bare-metal environments.

or, as mentioned earlier, if you want to go with dpdk, then there are
commercial offerings available there as well.

--
kind regards
anupam

  reply	other threads:[~2017-03-21 10:22 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
2017-03-21  9:30     ` Anupam Kapoor
2017-03-21  9:48       ` Ankit Aggarwal
2017-03-21 10:22         ` Anupam Kapoor [this message]
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=87bmsvgcab.fsf@gmail.com \
    --to=anupam.kapoor@gmail.com \
    --cc=ankit.a@irage.in \
    --cc=arybchenko@solarflare.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).