DPDK patches and discussions
 help / color / mirror / Atom feed
From: Alejandro Lucero <alejandro.lucero@netronome.com>
To: Pushpasis Sarkar <pushpasis@gmail.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [README]:Running DPDK in a LXC-based Container
Date: Thu, 11 Feb 2016 12:04:28 +0000	[thread overview]
Message-ID: <CAD+H992JyMPKho2MS0RxDpo5r7ogtbP49cgP113H5rO8Vnw5ug@mail.gmail.com> (raw)
In-Reply-To: <CAKV+TPhgY03fs3y4NyqO2GsYjo-xkVZeXLEFPc6OFU6sZNogcA@mail.gmail.com>

Did you try with the --file-prefix testpmd option?

Just use different file-prefix for each DPDK app running.

On Thu, Feb 11, 2016 at 5:01 AM, Pushpasis Sarkar <pushpasis@gmail.com>
wrote:

> Hi Krishna,
>
> Off-late I have been investigating DPDK on Linux containers.. I came across
> this thread and found it very helpful.. But I still find some issues when I
> try to run the same DPDK application simultaneously on more than one LXC
> containers..
>
> Even when following the example provided in this thread. I am unable to run
> the same application simultaneously in both host and more than one LXC
> containers..
> Is there any way to achieve the same..
>
> The basic issue I see in the DPDK design that kit assumes that it will use
> /mnt/huge/ file-path before using it.. making it unavailable to any other
> process.. Can this be changed to use the sub-directory /mnt/huge/$(uname
> -n)/<PID>. That way it cannot stop other process running on host/lxc from
> using the hugepages.. I have donot have much knowledge about how the
> hugepage filesystem works.. so pardon my ignorance... :)
>
> Looking forward to some help on this.
>
> Regards,
> -Pushpasis
>

  reply	other threads:[~2016-02-11 12:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11  5:01 Pushpasis Sarkar
2016-02-11 12:04 ` Alejandro Lucero [this message]
     [not found] ` <1455193461352.1476199754@boxbe>
2016-02-11 12:56   ` Pushpasis Sarkar
2016-02-11 13:08     ` Bruce Richardson
     [not found]     ` <1455197317303.1476199754@boxbe>
2016-02-11 16:19       ` Pushpasis Sarkar
  -- strict thread matches above, loose matches on Subject: below --
2015-06-17  6:01 Mohit Saxena
2014-10-08 13:44 Murthy, Krishna J
2014-10-10  0:26 ` Xie, Huawei

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=CAD+H992JyMPKho2MS0RxDpo5r7ogtbP49cgP113H5rO8Vnw5ug@mail.gmail.com \
    --to=alejandro.lucero@netronome.com \
    --cc=dev@dpdk.org \
    --cc=pushpasis@gmail.com \
    /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).