DPDK usage discussions
 help / color / mirror / Atom feed
From: Hamed Zaghaghi <hamed.zaghaghi@gmail.com>
To: Mahdi Moradmand Badie <mahdi.mbadie@gmail.com>
Cc: dev@dpdk.org, users@dpdk.org
Subject: Re: [dpdk-users] how to Read(Write) from(to) via lcores in dpdk regardless of NIC
Date: Tue, 08 Mar 2016 05:35:14 +0000	[thread overview]
Message-ID: <CAHPxn8b6PDsCCh5JE7g8xAtKSRj7Z9T0HarKw7FXHrWyDm3Sjw@mail.gmail.com> (raw)
In-Reply-To: <CAM=H7wfs3Y_rnEOSVCN8NsHm_DS58PM5Bpmm4Xo1Yf2RZD=Cnw@mail.gmail.com>

Hi,

If I understood well you need to do these tasks:
1. Packet crafting (I think that DPDK has no functions for this task)
2. Store packets (DPDK has (rte_mbuf)[
http://dpdk.org/doc/api/rte__mbuf_8h.html])
3. Share between lcores (DPDK offers rte_ring)



On Tue, Mar 8, 2016 at 8:45 AM Mahdi Moradmand Badie <mahdi.mbadie@gmail.com>
wrote:

> Dear Hamed,
>
> First of all thank you so much for your kindly reply,
>
> It's the primary part of the big project, in order to be more familiar
> with DPDK,
> I have to implement the mentioned framework by use of DPDK,
> And finally we wanna implement the cache locking approach (via help of
> features like Cache Allocation Technology(CAT), Cache Monitoring Technology
> (CMT)) in Xeon processor (my supervisor told me this simple exercise
> will be helpful to do the final part) in such a way we could dedicate a
> specific part of shared memory (L3) to each core which the other don't
> access to it.
> Obviously using of DPDK with Xeon which both are from "Intel", is
> considered as strength point.
>
> I hope this was more clear :)
>
> On 7 March 2016 at 23:56, Hamed Zaghaghi <hamed.zaghaghi@gmail.com> wrote:
>
>> Hi Mahdi,
>>
>> Why do you want to use DPDK when you don't use NIC? You can do what you
>> want outside of DPDK.
>>
>> Regards,
>> Hamed Zaghaghi
>>
>> On Tue, Mar 8, 2016 at 12:16 AM Mahdi Moradmand Badie <
>> mahdi.mbadie@gmail.com> wrote:
>>
>>> Dear All,
>>> I am Mahdi and I am new in DPDK,
>>> I wanna generate for example 3 different packets in core0 as master write
>>> it to share memory (L3), then core1 as slave read this packets, change
>>> them
>>> with for example function1 and write again in share memory (L3) and
>>> finally
>>> check the result with whatever I expect.
>>> The most important thing is that I don't wanna use NIC and I don't know
>>> for
>>> working with cores how I can write/read to/from them, I mean with which
>>> template and sequence???
>>> Thanks in advance,
>>>
>>
>
>
> --
> M@hdi Mor@dm@nd B@die
>

  reply	other threads:[~2016-03-08  5:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07 20:45 Mahdi Moradmand Badie
2016-03-08  4:56 ` Hamed Zaghaghi
2016-03-08  5:15   ` Mahdi Moradmand Badie
2016-03-08  5:35     ` Hamed Zaghaghi [this message]
2016-03-08  5:41       ` Mahdi Moradmand Badie
2016-03-08  8:17         ` [dpdk-users] [dpdk-dev] " Andriy Berestovskyy
     [not found]           ` <CAM=H7wdr5mYBeKunk2+aOE_6W2z8VoV1YjiwAsdj_dUtV4D1wQ@mail.gmail.com>
     [not found]             ` <CAM=H7wdgkmAoFaf+vtr4Zk4w1DZLWNdVXTSX4pWuPVj+VzxXDA@mail.gmail.com>
2016-03-08 21:49               ` Mahdi Moradmand Badie
2016-03-09 10:26                 ` Andriy Berestovskyy
     [not found]                   ` <CAM=H7weKrVPLm89E-Nwp-kvF39dTBukwwUOo_z+x=CeOhQgkOQ@mail.gmail.com>
2016-03-23 10:49                     ` Andriy Berestovskyy

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=CAHPxn8b6PDsCCh5JE7g8xAtKSRj7Z9T0HarKw7FXHrWyDm3Sjw@mail.gmail.com \
    --to=hamed.zaghaghi@gmail.com \
    --cc=dev@dpdk.org \
    --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).