DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Sylvain Vasseur <remmog@gmail.com>
Cc: users@dpdk.org
Subject: Re: poor performances with DPDK on a gcloud VM
Date: Tue, 21 Jun 2022 09:52:11 -0700	[thread overview]
Message-ID: <20220621095211.2de760cd@hermes.local> (raw)
In-Reply-To: <CABVe3HNM1wU=xqD3q-+NNcaCk4akNMgDBwhxcYXNk6LMGPeoFA@mail.gmail.com>

On Tue, 21 Jun 2022 17:29:38 +0100
Sylvain Vasseur <remmog@gmail.com> wrote:

> Hello,
> 
> Did someone already manage to use DPDK on a GCP VM and have good
> performances? I am trying this configuration lately, have some awful
> bandwidth results and no idea what I could be doing wrong.
> 
> I use the VirtIO interfaces on my VMs, was able to use both the vfio-pci
> and igb_uio PMD. But can only get ~350Mbps (yes bits!) with both, when
> trying to transmit data with a very basic testpmd run.
> dpdk-testpmd -a 0000:00:05.0 -- --forward-mode=txonly --stats-period 1
> 
> Any non-dpdk use of the network interface gives me way better results
> (GBps!).
> 
> Device:
> 00:05.0 Ethernet controller: Red Hat, Inc. Virtio network device
> 
> Bind status
> Network devices using DPDK-compatible driver
> ============================================
> 0000:00:05.0 'Virtio network device 1000' drv=igb_uio unused=vfio-pci
> 
> I would bet I am doing something wrong, either with the PMD choice, or with
> some setting. But can't figure what. Did anyone manage to have good
> performances or some experience of using DPDK on a google cloud VM?
> 
> Thanks in advance
> Sylvain

Check the negotiation of virtio features and checksum offload bits.

      reply	other threads:[~2022-06-21 16:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21 16:29 Sylvain Vasseur
2022-06-21 16:52 ` Stephen Hemminger [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=20220621095211.2de760cd@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=remmog@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).