From: "Chen, Jing D" <jing.d.chen@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
"Wang, Xiao W" <xiao.w.wang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] fm10k: fix VF cannot receive broadcast traffic
Date: Sun, 19 Jun 2016 13:47:36 +0000 [thread overview]
Message-ID: <4341B239C0EFF9468EE453F9E9F4604D044CEB6F@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20160617101833.GB14948@bricha3-MOBL3>
Hi, Bruce,
> -----Original Message-----
> From: Richardson, Bruce
> Sent: Friday, June 17, 2016 6:19 PM
> To: Wang, Xiao W <xiao.w.wang@intel.com>
> Cc: Chen, Jing D <jing.d.chen@intel.com>; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] fm10k: fix VF cannot receive broadcast
> traffic
>
> On Mon, Jun 06, 2016 at 05:00:47PM +0800, Wang Xiao W wrote:
> > When app tries promisc/allmulti setting, fm10k will check if a valid
> > glort is acquired, if not then exit without doing anything. It's a
> > long journey for VF to acquire glort info from VF to PF mailbox, PF to switch
> mailbox.
> > It could be a long interval that's out of DPDK's control. Thus, app
> > may
>
> I think the use of "thus" here is wrong, as I suspect that the failure is not due
> to the "long interval that's out of DPDK's control", but instead due to not
> having a valid glort.
The logic in VF is glort ID is invalid at beginning. When VF port is enabled by
sending mailbox to PF, PF will send a message back to VF without carrying valid
info. Then, VF will fake a glort ID.
In this case, it's useless to do sanity check of VALID glort ID. Besides that, VF didn't
use glort ID to do functional call at all.
>
> > fail on promisc/allmulti setting in VF. In fact, we don't need a valid
> > glort value in VF, so this patch just skips the glort check for VF.
> >
> > Fixes: df02ba864695 ("fm10k: support promiscuous mode")
> >
> > Signed-off-by: Wang Xiao W <xiao.w.wang@intel.com>
>
> I rework this commit message for you on apply. Please check the updated
> version when done.
>
> /Bruce
prev parent reply other threads:[~2016-06-19 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 9:00 Wang Xiao W
2016-06-14 5:03 ` Chen, Jing D
2016-06-17 10:32 ` Bruce Richardson
2016-06-17 10:18 ` Bruce Richardson
2016-06-19 13:47 ` Chen, Jing D [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=4341B239C0EFF9468EE453F9E9F4604D044CEB6F@shsmsx102.ccr.corp.intel.com \
--to=jing.d.chen@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=xiao.w.wang@intel.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).