From: Cody Doucette <doucette@bu.edu>
To: Alex Kiselev <kiselev99@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] KNI interfaces at bonding ports
Date: Thu, 22 Jun 2017 12:08:19 -0400 [thread overview]
Message-ID: <CAJjX64Y=qkDoC+Ny7MNA+Ni=i44X=yUBPKe88yQK2nS8MGK0cQ@mail.gmail.com> (raw)
In-Reply-To: <CAMKNYbx0M+=7gMnJGKE7ZS24=Fy7Xsap2PuNcteeXk36NS5WiA@mail.gmail.com>
Hi Alex,
I previously ran into the same issue. I just used the PCI device
information from the primary slave of the bonded interface:
https://github.com/AltraMayor/gatekeeper/blob/master/cps/main.c#L545
Hope that helps,
Cody
On Thu, Jun 22, 2017 at 5:06 AM, Alex Kiselev <kiselev99@gmail.com> wrote:
> Hello.
>
> Is it possible to create a KNI interface at a bonding port?
>
> My code that works perfectly fine with usual dpdk ports fails
> when I try to use it with bonding ports.
>
> rte_eth_dev_info_get(port_id, &dev_info);
> conf.addr = dev_info.pci_dev->addr;
> ...
> return rte_kni_alloc(pktmbuf_pool, &conf, &ops);
>
>
> The code fails because pci_dev member of variable dev_info is NULL.
> Is there any workarounds for this problem?
>
> Thanks.
>
> --
> Alexander Kiselev
>
next prev parent reply other threads:[~2017-06-22 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 9:06 Alex Kiselev
2017-06-22 16:08 ` Cody Doucette [this message]
2017-06-22 20:25 ` Alex Kiselev
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='CAJjX64Y=qkDoC+Ny7MNA+Ni=i44X=yUBPKe88yQK2nS8MGK0cQ@mail.gmail.com' \
--to=doucette@bu.edu \
--cc=kiselev99@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).