From: madhukar mythri <madhukar.mythri@gmail.com>
To: Jonas Nemeiksis <jnemeiksis@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] ovs-dpdk issue
Date: Tue, 4 Jun 2019 12:41:22 +0530 [thread overview]
Message-ID: <CAAUNki0=hG2ZhTGP6PV8veoXTxZOSFh7tYRJv+BBE-5RWqZ=cw@mail.gmail.com> (raw)
In-Reply-To: <CAEsDSunfeZyTQxLtGVFb5O+azwoZbJiZ8t+DARuYjO3zhQgukQ@mail.gmail.com>
You can go-through this OVS+DPDK link on Performance tunning details:
http://docs.openvswitch.org/en/latest/intro/install/dpdk/
In which, you can goto "Performance-Tunning" section which explains about
the CPU isolation (makesure, you have done Core to Rx-queue binding) and
Memory allocated as per NUMA-node.
Regards,
Madhukar.
On Mon, Jun 3, 2019 at 6:02 PM Jonas Nemeiksis <jnemeiksis@gmail.com> wrote:
> Hi all!
>
> I have problems with ovs-dpdk throughput. I found some information about
> TSO , also I'm not clear how I can right turn on it.
>
> I tried a lot options but throughput very poor.
>
> DPDK: 18.11.1
> OVS: 2.11.1
>
> Maybe anyone have practices with it and could share best practices?
>
>
> Thank you!
>
prev parent reply other threads:[~2019-06-04 7:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 8:27 Jonas Nemeiksis
2019-06-04 7:11 ` madhukar mythri [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='CAAUNki0=hG2ZhTGP6PV8veoXTxZOSFh7tYRJv+BBE-5RWqZ=cw@mail.gmail.com' \
--to=madhukar.mythri@gmail.com \
--cc=jnemeiksis@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).