patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Xing, Beilei" <beilei.xing@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] net/i40e: fix no response from kernel PF
Date: Mon, 17 Jul 2017 07:20:24 +0000	[thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F810DC8D32@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1500275587-76019-1-git-send-email-beilei.xing@intel.com>



> -----Original Message-----
> From: Xing, Beilei
> Sent: Monday, July 17, 2017 3:13 PM
> To: Wu, Jingjing <jingjing.wu@intel.com>
> Cc: stable@dpdk.org
> Subject: [PATCH] net/i40e: fix no response from kernel PF

net/i40e: fix virtchnl message response timeout

> 
> If using old kernel driver and using kernel PF and DPDK VF mode, VF fails to
> start due to incomplete command.

PF driver and VF driver communicated with each other by virtual channel
message. When VF sends to message to PF to enable some offload capability,
PF should response if it is successful or not.

VIRTCHNL_OP_ENABLE_VLAN_STRIPPING is a new added message and the old
PF driver doesn't support that. So no response is received by DPDK VF. Then
VF is blocked on this message and cannot roll back.

> The root cause is that old kernel driver doesn't support vlan stripping, when
> DPDK VF sends VIRTCHNL_OP_ENABLE_VLAN_STRIPPING to kernel PF, PF won't
> response to VF.
> This patch adds clearing command on VF side if PF won't response to VF, avoids
> blocking the following commands.

This patch clears the pending command on VF side when the waiting duration
expires to avoid blocking following communication.

      reply	other threads:[~2017-07-17  7:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17  7:13 Beilei Xing
2017-07-17  7:20 ` Wu, Jingjing [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=9BB6961774997848B5B42BEC655768F810DC8D32@SHSMSX103.ccr.corp.intel.com \
    --to=jingjing.wu@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=stable@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).