DPDK usage discussions
 help / color / mirror / Atom feed
From: Kusuma DS <kusumanjali47@gmail.com>
To: shaklee3@gmail.com
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Question on Multiple process support Application
Date: Mon, 12 Nov 2018 09:37:39 +0530	[thread overview]
Message-ID: <CABN7GFEXGPaP_yY-TrC=LoeFLMtDLx8NN9uZhx4Zs4R+XCXZdw@mail.gmail.com> (raw)
In-Reply-To: <CA+Gp1na4pLLDXqK6fthYo_C6=EtUnbrDao1QwZC9OdsapCiFwQ@mail.gmail.com>

Thanks for the information.

On Mon, Nov 5, 2018 at 7:16 PM Cliff Burdick <shaklee3@gmail.com> wrote:

>
>
>
> On Mon, Nov 5, 2018, 04:56 Kusuma DS <kusumanjali47@gmail.com wrote:
>
>> Hii,
>>
>> I have some doubts regarding multiple process example application.
>>
>> I have 2 processes running in my setup using multiprocess client and
>> server
>> concept, am doing rx_burst in server process and tx_burst in client
>> process. But the thing is i have one isolated cpu, So both the process are
>> sharing the cpu.
>>
>> What i understand through the document provided by the dpdk is  In the
>> concept of memory pool there will be per core cache lock, so if we try to
>> do tx and rx in different process there will be software cache problem
>> will
>> occur, so there will be corrupting the memory in shared memory pool.
>>
>> How to resolve this issue??If anyone Know about this issue please let me
>> know.
>>
>
> The documentation specifies you can't lcores across processes:
>
> "All DPDK processes running as a single application and using shared
> memory must have distinct coremask/corelist arguments. It is not possible
> to have a primary and secondary instance, or two secondary instances, using
> any of the same logical cores. Attempting to do so can cause corruption of
> memory pool caches, among other issues."
>
> Have you tried two cores?
>
>
>> Thanks,
>> Kusuma
>>
>

      reply	other threads:[~2018-11-12  4:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-05 12:56 Kusuma DS
2018-11-05 13:45 ` Cliff Burdick
2018-11-12  4:07   ` Kusuma DS [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='CABN7GFEXGPaP_yY-TrC=LoeFLMtDLx8NN9uZhx4Zs4R+XCXZdw@mail.gmail.com' \
    --to=kusumanjali47@gmail.com \
    --cc=shaklee3@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).