DPDK usage discussions
 help / color / mirror / Atom feed
From: Matt Laswell <laswell@infiniteio.com>
To: Mahdi Moradmand Badie <mahdi.mbadie@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] Send and Receive packets to/from specific core
Date: Fri, 11 Mar 2016 14:29:59 -0600	[thread overview]
Message-ID: <CA+GnqArBQ5jQKnunWCDSOxQVCoYj1PCWZF1ghZJ5Op4sk60o7Q@mail.gmail.com> (raw)
In-Reply-To: <CAM=H7wfXquXkEEQ=UA-dmT0Ffppbqu4qZfU3bZKdLZ6aot11Vw@mail.gmail.com>

The easiest way to do what you're wanting to do is to use a message ring.
Take a look at the documentation for rte_ring here to see how it works:

http://dpdk.org/doc/api/rte__ring_8h.html

On Fri, Mar 11, 2016 at 2:22 PM, Mahdi Moradmand Badie <
mahdi.mbadie@gmail.com> wrote:

> Dear All,
>
> I wanna Send(write) a Packet(s) with specific data (for example x = 10)
> from core 0 to share memory and Receive (Read) it with another Core (for
> example Core 1), change it in Core 1 (for example X = X + 1) and write
> again in share memory.
> I really don't know How I could do it, I wanna do this without using NIC ot
> rte_eth at all, so simple and easy but I confused.
> Please help me.
>
> PS. I know there are many example do more complex than this small exercise
> but all did it via NIC.
>
> --
> M@hdi Mor@dm@nd B@die
>

  reply	other threads:[~2016-03-11 20:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 20:22 Mahdi Moradmand Badie
2016-03-11 20:29 ` Matt Laswell [this message]
2016-03-11 20:43 ` Kyle Larose
2016-03-11 20:47   ` Mahdi Moradmand Badie
2016-03-11 20:54     ` Kyle Larose
2016-03-11 21:01       ` Mahdi Moradmand Badie
2016-03-11 21:50         ` Kyle Larose
2016-03-11 22:19           ` Mahdi Moradmand Badie
2016-03-14 17:37             ` Mahdi Moradmand Badie
2016-03-16 13:25             ` Kyle Larose

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=CA+GnqArBQ5jQKnunWCDSOxQVCoYj1PCWZF1ghZJ5Op4sk60o7Q@mail.gmail.com \
    --to=laswell@infiniteio.com \
    --cc=mahdi.mbadie@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).