DPDK usage discussions
 help / color / mirror / Atom feed
From: Vincent Li <vincent.mc.li@gmail.com>
To: Pavel Vajarov <freakpv@gmail.com>
Cc: Vincent Li <vincent.mc.li@gmail.com>,
	 dave seddon <dave.seddon.ca@gmail.com>,
	 Stephen Hemminger <stephen@networkplumber.org>,
	users <users@dpdk.org>
Subject: Re: [dpdk-users] Peformance troubleshouting of TCP/IP stack over DPDK.
Date: Thu, 21 May 2020 09:31:05 -0700 (PDT)	[thread overview]
Message-ID: <alpine.OSX.2.21.2005210926570.38348@sea-ml-00029224.olympus.f5net.com> (raw)
In-Reply-To: <CAK9EM18KYgQnPrEj-cH84rhjcUHVkf1R98JkWD9ChBRm8S2_iw@mail.gmail.com>



On Thu, 21 May 2020, Pavel Vajarov wrote:

>       I am curious how you get F-Stack working with KVM VM with SR-IOV. The
>       author of F-Stack mentioned F-Stack not tested working for KVM VM. I had
>       an issue report here: https://github.com/F-Stack/f-stack/issues/489
> 
> 
> Hi there,
> 
> I asked our admin who setup the KVM for the tests.
> He said that this parameter has been given to the QEMU:
>  -device vfio-pci,host=af:00.2,id=hostdev0,bus=pci.0,addr=0x9
> 
> This is how the device configuration looks in the XML:
> <hostdev mode='subsystem' type='pci' managed='yes'>
>       <driver name='vfio'/>
>       <source>
>         <address domain='0x0000' bus='0xaf' slot='0x00' function='0x2'/>
>       </source>
>       <alias name='hostdev0'/>
>       <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
>     </hostdev>
> 
> Here is how the things are seen from the guest machine:
> 00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device    <----- This device is used for SSH access to the server
> 00:09.0 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 02)   <------ This is the 10Gpbs card used for the tests.

this seems to be passing the PF to guest, not SR-IOV VF. I am wondering 
what happens if you use SR-IOV and pass VF to guest, you may run into same 
issue as I did.

> 
> Network devices using DPDK-compatible driver
> ============================================
> 0000:00:09.0 'Ethernet Controller X710 for 10GbE SFP+ 1572' drv=igb_uio unused=i40e
> 
> Network devices using kernel driver
> ===================================
> 0000:00:03.0 'Virtio network device 1000' if=ens3 drv=virtio-pci unused=igb_uio *Active*
> 
> Hope that helps.
> 
> Regards,
> Pavel.
> 
> 

  reply	other threads:[~2020-05-21 16:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06  5:14 Pavel Vajarov
2020-05-06 14:54 ` Stephen Hemminger
2020-05-07 10:47   ` Pavel Vajarov
2020-05-07 14:09     ` dave seddon
2020-05-07 20:31       ` Stephen Hemminger
2020-05-08  5:03         ` Pavel Vajarov
2020-05-20 19:43       ` Vincent Li
2020-05-21  8:09         ` Pavel Vajarov
2020-05-21 16:31           ` Vincent Li [this message]
2020-05-26 16:50 ` Vincent Li
2020-05-27  5:11   ` Pavel Vajarov
2020-05-27 16:44     ` Vincent Li

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=alpine.OSX.2.21.2005210926570.38348@sea-ml-00029224.olympus.f5net.com \
    --to=vincent.mc.li@gmail.com \
    --cc=dave.seddon.ca@gmail.com \
    --cc=freakpv@gmail.com \
    --cc=stephen@networkplumber.org \
    --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).