From: "Björn Töpel" <bjorn.topel@gmail.com>
To: "Xu, Qian Q" <qian.q.xu@intel.com>
Cc: "Yao, Lei A" <lei.a.yao@intel.com>,
"Topel, Bjorn" <bjorn.topel@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] l3fwd can't launch on VF when we use i40e
Date: Wed, 10 Aug 2016 13:00:40 +0200 [thread overview]
Message-ID: <CAJ+HfNhisHk0+tRsS5XOR3w=zyDFNiH+UxLSsg8ioC1_nATcBg@mail.gmail.com> (raw)
In-Reply-To: <82F45D86ADE5454A95A89742C8D1410E032F7520@shsmsx102.ccr.corp.intel.com>
Firstly, sorry about the late reply.
> From my view, crc-strip is not a "MUST" check for the port start. We can configure the value after
> the port start.
> Any thoughts?
>From my perspective, a non-supported configuration should return an
error code to the API user.
> Do you know is there any way I can bypass this when I use l3fwd?
One work-around is enabling .hw_strip_crc for i40 VFs at runtime, by
e.g. using rte_eth_dev_info_get() to determine what driver that's in
use. That, however, does require a l3fwd patch.
Björn
prev parent reply other threads:[~2016-08-10 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2DBBFF226F7CF64BAFCA79B681719D9502044162@shsmsx102.ccr.corp.intel.com>
2016-07-22 2:10 ` Xu, Qian Q
2016-08-10 11:00 ` Björn Töpel [this message]
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='CAJ+HfNhisHk0+tRsS5XOR3w=zyDFNiH+UxLSsg8ioC1_nATcBg@mail.gmail.com' \
--to=bjorn.topel@gmail.com \
--cc=bjorn.topel@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=lei.a.yao@intel.com \
--cc=qian.q.xu@intel.com \
--cc=thomas.monjalon@6wind.com \
/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).