DPDK patches and discussions
 help / color / mirror / Atom feed
From: Mats Liljegren <liljegren.mats2@gmail.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] How to debug packet sends to virtual functions
Date: Mon, 17 Feb 2014 13:29:06 +0100	[thread overview]
Message-ID: <CA+xJJ1_QNi=XwTxvV3mxyjt02teR4ObtB00xE_PEDp9va4nf3g@mail.gmail.com> (raw)
In-Reply-To: <C6ECDF3AB251BE4894318F4E45123697591F915F@IRSMSX101.ger.corp.intel.com>

Hi Anatoly,

>> The guest starts with loading the igbvf kernel driver, uses ifconfig <dev> up,
>> then loads and binds to igb_uio. After that, DPDK works. If I skip any step
>> here it doesn't work. Skipping "ifconfig" step resulted in packets being
>> received but I couldn't send them, they just got queued up but was never
>> sent.
>>
>
> Hm, never seen this before. Apologies if you have already mentioned this, but what NIC are you using? I'll see if I can replicate your issues.

Not sure if I've mentioned it, but it is a quad I350. Port 0 and 3 on
host only, and 1 and 2 are being used by DPDK in a guest. The
challenge was to make a ping go from port 0 to 3 and back, via a
somewhat modified DPDK l2fwd example. Port 1 and 2 had two virtual
functions each, and each such pair was given to an instance of this
l2fwd example.

>> It's the latter, i.e. two primary processes running DPDK on the same VM but
>> different VF devices. The VF devices belongs to the same physical devices
>> though.
>
> I'll try that as well.

If you need more help with how we set things up, I'll be happy to help you.

Regards
Mats Liljegren

  reply	other threads:[~2014-02-17 12:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29 17:56 Mats Liljegren
2014-01-31 18:30 ` Mats Liljegren
2014-02-03 11:13   ` Mats Liljegren
2014-02-04 10:08     ` Mats Liljegren
2014-02-04 10:26       ` jigsaw
2014-02-04 10:45         ` Mats Liljegren
2014-02-04 11:14           ` jigsaw
2014-02-04 11:31             ` Mats Liljegren
2014-02-04 12:11               ` jigsaw
2014-02-04 11:21           ` Burakov, Anatoly
2014-02-04 11:47             ` Mats Liljegren
2014-02-04 11:52               ` Burakov, Anatoly
2014-02-04 13:03                 ` Mats Liljegren
2014-02-04 13:40                   ` Burakov, Anatoly
2014-02-13 15:32                     ` Mats Liljegren
2014-02-13 15:39                       ` Burakov, Anatoly
2014-02-17 11:05                         ` Mats Liljegren
2014-02-17 12:11                           ` Burakov, Anatoly
2014-02-17 12:29                             ` Mats Liljegren [this message]
2014-02-17 14:35                               ` Mats Liljegren
2014-02-17 14:36                                 ` Burakov, Anatoly

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='CA+xJJ1_QNi=XwTxvV3mxyjt02teR4ObtB00xE_PEDp9va4nf3g@mail.gmail.com' \
    --to=liljegren.mats2@gmail.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@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).