From: chetan bhasin <chetan.bhasin017@gmail.com>
To: 3chas3@gmail.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Getting issue while bringin Bond with VMXNET3 (DPDK 17.11)
Date: Tue, 9 Oct 2018 10:05:54 +0530 [thread overview]
Message-ID: <CACZZ+Y5tPnCKwb23JAJtw7GaVOZJ8aAKbrOVd3NT6XxP8UYyZQ@mail.gmail.com> (raw)
In-Reply-To: <48d92b8e-a2fd-0818-e65d-e38560d5f5c0@gmail.com>
Thanks for your reply .
The issue coming in function "vmxnet3_dev_tx_queue_setup"
below if condition is true because "tx_conf->txq_flags is coming as 0"
if ((tx_conf->txq_flags & ETH_TXQ_FLAGS_NOXSUMSCTP) !=
ETH_TXQ_FLAGS_NOXSUMSCTP) {
PMD_INIT_LOG(ERR, "SCTP checksum offload not supported");
return -EINVAL;
}
Regards,
Chetan Bhasin
On Tue, Oct 9, 2018 at 7:11 AM Chas Williams <3chas3@gmail.com> wrote:
> Any other error messages? There's really only one path out of
> slave_configure() that doesn't emit another error message and
> that's slave_configure_slow_queue. You need to set dedicated_queues to
> be enabled to see that happen.
>
> On 10/07/18 01:12, chetan bhasin wrote:
> > Can anybody suggest? Stuck right now!
> >
> > On Sat, Oct 6, 2018, 17:02 chetan bhasin <chetan.bhasin017@gmail.com>
> wrote:
> >
> >> Hi Dpdk Champs,
> >>
> >> I am facing an issue while bringing bonding on VM having vmxnet3
> >> interfaces.
> >>
> >> Below error is coming in the log -
> >>
> >> PMD: bond_ethdev_start(1959) - bonded port (2) failed to reconfigure
> slave
> >> device (0).
> >>
> >> Please suggest.
> >>
> >> Thanks,
> >> Chetan Bhasin
> >>
>
next prev parent reply other threads:[~2018-10-09 4:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-06 11:32 chetan bhasin
2018-10-07 5:12 ` chetan bhasin
2018-10-09 1:41 ` Chas Williams
2018-10-09 4:35 ` chetan bhasin [this message]
2018-10-09 7:59 ` Ferruh Yigit
2018-10-09 8:18 ` chetan bhasin
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=CACZZ+Y5tPnCKwb23JAJtw7GaVOZJ8aAKbrOVd3NT6XxP8UYyZQ@mail.gmail.com \
--to=chetan.bhasin017@gmail.com \
--cc=3chas3@gmail.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).