DPDK usage discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: David Aldrich <David.Aldrich@EMEA.NEC.COM>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Beginner question: UDP Echo Server Example?
Date: Mon, 7 Nov 2016 22:45:55 +0000	[thread overview]
Message-ID: <C5F248A5-0D0B-42A9-AEB9-C70F93EA18ED@intel.com> (raw)
In-Reply-To: <1f5e819847824f57b68503846d9c2765@EUX13SRV1.EU.NEC.COM>


> On Nov 7, 2016, at 8:41 AM, David Aldrich <David.Aldrich@EMEA.NEC.COM> wrote:
> 
> Hi
> 
> I am just getting started with DPDK. I want to send and receive UDP packets using DPDK.  I saw a reference to a UDP Echo Server example, which I think would help me, but can't find the code.  Is that example still available?

DPDK does not have a UDP protocol stack, but you can decode and encode UDP frames in code you write. You may have seen the TLDK UDP echo example, which is located in FD.io community.

https://wiki.fd.io/view/TLDK

> 
> Best regards
> 
> David
> 

Regards,
Keith

      reply	other threads:[~2016-11-07 22:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-07 16:41 David Aldrich
2016-11-07 22:45 ` Wiles, Keith [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=C5F248A5-0D0B-42A9-AEB9-C70F93EA18ED@intel.com \
    --to=keith.wiles@intel.com \
    --cc=David.Aldrich@EMEA.NEC.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).