DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Eelco Chaudron" <echaudro@redhat.com>
To: "Ye Xiaolong" <xiaolong.ye@intel.com>
Cc: "Zhang, Xiao" <xiao.zhang@intel.com>,
	dev@dpdk.org, "Xing, Beilei" <beilei.xing@intel.com>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/i40e: always re-program promiscuous mode on VF interface
Date: Wed, 18 Dec 2019 09:33:41 +0100	[thread overview]
Message-ID: <11CB6A5A-1E92-4C24-A546-4078C2C1B1EC@redhat.com> (raw)
In-Reply-To: <20191218025732.GS59123@intel.com>

Thanks!



On 18 Dec 2019, at 3:57, Ye Xiaolong wrote:

> On 12/18, Zhang, Xiao wrote:
>>
>>> -----Original Message-----
>>> From: Eelco Chaudron [mailto:echaudro@redhat.com]
>>> Sent: Tuesday, November 19, 2019 9:45 PM
>>> To: Xing, Beilei <beilei.xing@intel.com>; Zhang, Qi Z 
>>> <qi.z.zhang@intel.com>
>>> Cc: Zhang, Xiao <xiao.zhang@intel.com>; dev@dpdk.org
>>> Subject: [PATCH v2] net/i40e: always re-program promiscuous mode on 
>>> VF
>>> interface
>>>
>>> During a kernel PF reset, this event is propagated to the VF.
>>> The DPDK VF PMD will execute the reset task before the PF is done 
>>> with his. This
>>> results in the admin queue message not being responded to leaving 
>>> the port in
>>> "promiscuous" mode.
>>>
>>> This patch makes sure the promiscuous mode is configured 
>>> independently of the
>>> current admin state.
>>>
>>> Signed-off-by: Eelco Chaudron <echaudro@redhat.com>
>>
>> Reviewed-by: Xiao Zhang <xiao.zhang@intel.com>
>
> Applied to dpdk-next-net-intel, Thanks.


      reply	other threads:[~2019-12-18  8:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 13:45 Eelco Chaudron
2019-12-04 15:18 ` Eelco Chaudron
2019-12-17 13:50   ` Eelco Chaudron
2019-12-18  1:23 ` Zhang, Xiao
2019-12-18  2:57   ` Ye Xiaolong
2019-12-18  8:33     ` Eelco Chaudron [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=11CB6A5A-1E92-4C24-A546-4078C2C1B1EC@redhat.com \
    --to=echaudro@redhat.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.com \
    --cc=xiao.zhang@intel.com \
    --cc=xiaolong.ye@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).