DPDK usage discussions
 help / color / mirror / Atom feed
From: Alex Zelichenko <alex@scadafence.com>
To: shaklee3@gmail.com
Cc: users@dpdk.org
Subject: Re: [dpdk-users] error running bonding example - Rx offloads capabilities 0x0 in rte_eth_dev_configure()
Date: Wed, 5 Dec 2018 16:59:00 +0200	[thread overview]
Message-ID: <CAPbBVQjwFKuxPeAmEXRzZ_nJEYcKbPRB84AsmbKTdF-9qGhtJQ@mail.gmail.com> (raw)
In-Reply-To: <CA+Gp1nZ8tgwyCDH=qirXmszPw_RgKbkTR5cod_AitCqTX9FneA@mail.gmail.com>

It's *gcc (Ubuntu 4.8.4-2ubuntu1~14.04.4) 4.8.4*


On Wed, Dec 5, 2018 at 3:53 PM Cliff Burdick <shaklee3@gmail.com> wrote:

> Before going there, can you describe your compiler version? The code
> should have worked as-is I think, so it would be good to understand what
> broke.
>
> On Wed, Dec 5, 2018, 02:36 Alex Zelichenko <alex@scadafence.com wrote:
>
>> Great, it worked (10x!). There's no error any more. But how do I interact
>> with that bond port? For now it behaves like network stub. Just collects
>> stats. Can I feed it to kni?
>>
>> On Tue, Dec 4, 2018 at 6:59 PM Cliff Burdick <shaklee3@gmail.com> wrote:
>>
>>> Can you try zeroing out the offloads flag at the top?
>>>
>>>         .rxmode = {
>>>                 .mq_mode = ETH_MQ_RX_NONE,
>>>                 .max_rx_pkt_len = ETHER_MAX_LEN,
>>>                 .split_hdr_size = 0,
>>>                 .offloads = 0,
>>>         },
>>>
>>>
>>> On Tue, Dec 4, 2018 at 12:53 AM Alex Zelichenko <alex@scadafence.com>
>>> wrote:
>>>
>>>> Hi, I am running provided *bond_app* for 2 ports (bound to igb_uio), and
>>>> the log I get is as follows:
>>>> alex@alex-lab:~/dpdk-stable-18.05.1$ sudo
>>>> ./examples/bond/build/bond_app
>>>> -l 2-7 -n 2 -m --huge-dir /mnt/huge -- -p 3 -P
>>>> --config="(0,2,3,7),(1,4,5,6)"
>>>> EAL: Detected 8 lcore(s)
>>>> EAL: Detected 1 NUMA nodes
>>>> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
>>>> EAL: No free hugepages reported in hugepages-1048576kB
>>>> EAL: Probing VFIO support...
>>>> EAL: PCI device 0000:00:1f.6 on NUMA socket -1
>>>> EAL:   Invalid NUMA socket, default to 0
>>>> EAL:   probe driver: 8086:15b7 net_e1000_em
>>>> EAL: PCI device 0000:03:00.0 on NUMA socket -1
>>>> EAL:   Invalid NUMA socket, default to 0
>>>> EAL:   probe driver: 8086:1528 net_ixgbe
>>>> EAL: PCI device 0000:03:00.1 on NUMA socket -1
>>>> EAL:   Invalid NUMA socket, default to 0
>>>> EAL:   probe driver: 8086:1528 net_ixgbe
>>>> User device list:
>>>> Port 0 MAC: b4:96:91:21:a2:6c
>>>> Port 1 MAC: b4:96:91:21:a2:6e
>>>> ethdev port_id=2 requested Rx offloads 0x1000 doesn't match Rx offloads
>>>> capabilities 0x0 in rte_eth_dev_configure()
>>>>
>>>> Port 2 MAC: b4:96:91:21:a2:6c
>>>> Starting lcore_main on core 3:0 Our IP:7.0.0.10
>>>> bond6>
>>>>
>>>> How do I get rid of that error on bond port? How do I get that bond
>>>> interface? I can't see anything in the system that is related to
>>>> *net_bonding0*
>>>> --
>>>> Best,
>>>> Alex Z
>>>>
>>>
>>

  reply	other threads:[~2018-12-05 14:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04  8:52 Alex Zelichenko
2018-12-04 16:58 ` Cliff Burdick
2018-12-05 10:36   ` Alex Zelichenko
2018-12-05 13:53     ` Cliff Burdick
2018-12-05 14:59       ` Alex Zelichenko [this message]
2018-12-10  6:13         ` Alex Zelichenko
2018-12-11 10:08           ` Gowrishankar Muthukrishnan

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=CAPbBVQjwFKuxPeAmEXRzZ_nJEYcKbPRB84AsmbKTdF-9qGhtJQ@mail.gmail.com \
    --to=alex@scadafence.com \
    --cc=shaklee3@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).