From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: Kai Zhang <zhang.4522@osu.edu>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Running independent processes on the same machine
Date: Sun, 20 Jul 2014 19:15:33 +0000 [thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B0343B0A39@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <CACKSPmdz-LxpezPfn7UxBkTRFCoWXhQnO-qhEd+4UwMdHw-7sA@mail.gmail.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Kai Zhang
> Sent: Sunday, July 20, 2014 11:04 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Running independent processes on the same machine
>
> Hello,
>
> I have been trying to measure the round trip latency with two machines,
> A->B->A. I modified l2fwd as two new apps: rx and tx, where tx sends
> packets and embeds time stamp, rx receives packets and calculate the round
> trip latency.
> The source code are as follows:
> https://github.com/kay21s/dpdk/tree/master/examples/rx
> https://github.com/kay21s/dpdk/tree/master/examples/tx
>
> Both of rx and tx run correctly if only one app is running. However, when I
> am trying to run rx and tx simultaneously on machine A, rx cannot receive
> any packets.
> The commands I used are
>
>
> sudo ./build/tx -c 0x2 -n 1 --file-prefix p2 -m 64 -- -q 1 -p 1
> sudo ./build/rx -c 0x1 -n 1 --file-prefix p1 -m 64 -- -q 1 -p 1
>
> Thanks for your help,
> Kai
Hi Kai,
Two independent processes on the same machine cannot share Ethernet ports as each will reconfigure the ports for its own use when it runs. To run independent processes, you need to assign unique ports to each one and blacklist the ports being used by any other processes so that the new process doesn't reset those ports and stop the other processes from working.
Regards,
/Bruce
next prev parent reply other threads:[~2014-07-20 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 18:03 Kai Zhang
2014-07-20 19:15 ` Richardson, Bruce [this message]
2014-07-21 0:19 ` Kai Zhang
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=59AF69C657FD0841A61C55336867B5B0343B0A39@IRSMSX103.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=zhang.4522@osu.edu \
/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).