From: Ben Pfaff <blp@ovn.org>
To: abhishek jain <ashujain9727@gmail.com>
Cc: ovs-discuss@openvswitch.org, dev@dpdk.org
Subject: Re: [dpdk-dev] Tx/Rx count not increasing OVS-DPDK
Date: Wed, 29 Nov 2017 09:13:27 -0800 [thread overview]
Message-ID: <20171129171327.GL13883@ovn.org> (raw)
In-Reply-To: <CA+9-LvvaOANBC_G8c-bmHESpZUtBDMbf+W7iwNHO5GsLL_YYVQ@mail.gmail.com>
On Wed, Nov 29, 2017 at 10:57:12AM +0530, abhishek jain wrote:
> I'm having 2 VMs running with ovs-dpdk as a networking agent on
> openstack compute node.
> When I'm checking the external connectivity of the VMs by pinging to
> the external world,the Tx/Rx count of the VMs is not increasing.
>
>
> However I'm able to ping the local-Ip of the respective Vms.
> Let me know the possible solution for this.
I don't know why you're writing to me specifically here. I am not an
expert on OVS-DPDK or on OpenStack.
parent reply other threads:[~2017-11-29 17:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CA+9-LvvaOANBC_G8c-bmHESpZUtBDMbf+W7iwNHO5GsLL_YYVQ@mail.gmail.com>]
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=20171129171327.GL13883@ovn.org \
--to=blp@ovn.org \
--cc=ashujain9727@gmail.com \
--cc=dev@dpdk.org \
--cc=ovs-discuss@openvswitch.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).