DPDK usage discussions
 help / color / mirror / Atom feed
From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Tushar Mulkar <tusharmulkar@gmail.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] PF link status is not getting detected correctly by dpdk driver in VM
Date: Thu, 11 Jan 2018 14:43:11 +0000	[thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA650FED9C7@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <CAGWHT4-CG9sorZNTZykzn5mbNHfTLnom6fcx6aBOAWR4+00q1A@mail.gmail.com>

> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Tushar Mulkar
> Sent: Thursday, January 11, 2018 1:55 PM
> To: users@dpdk.org
> Subject: Re: [dpdk-users] PF link status is not getting detected correctly
> by dpdk driver in VM
> 
> Hi All,

Hi!


> So finally I am able to find the issue.  Actually in dpdk i40evf driver,
> the way link up/down is propagated is not working for me. Below change set
> worked for me.

Please send a patch to dev@dpdk.org (http://dpdk.org/doc/guides/contributing/patches.html)

In the commit message, please describe the issue a bit more, and how the patch
fixes it. Also add a "signoff" so it can be accepted into the DPDK source.

Also CC the i40e maintainers to bring it to their attention.
From the MAINTAINERS file, i40e heading:
Beilei Xing <beilei.xing@intel.com>
Qi Zhang <qi.z.zhang@intel.com>


Regards, -Harry


> diff --git a/drivers/net/i40e/i40e_ethdev_vf.c
> b/drivers/net/i40e/i40e_ethdev_vf.c
> index 87a760796..0389f4bfa 100644
> --- a/drivers/net/i40e/i40e_ethdev_vf.c
> +++ b/drivers/net/i40e/i40e_ethdev_vf.c
> @@ -2235,13 +2235,13 @@ i40evf_dev_link_update(struct rte_eth_dev *dev,
>                 new_link.link_speed = ETH_SPEED_NUM_100M;
>                 break;
>         }
> +
>         /* full duplex only */
>         new_link.link_duplex = ETH_LINK_FULL_DUPLEX;
> -       new_link.link_status = vf->link_up ? ETH_LINK_UP :
> -                                            ETH_LINK_DOWN;
> +    new_link.link_status = (vf->link_up & true) ? ETH_LINK_UP :
> +                                            ETH_LINK_DOWN;
> 
>         i40evf_dev_atomic_write_link_status(dev, &new_link);
> -
>         return 0;
>  }
> 
> 

<snip>


      reply	other threads:[~2018-01-11 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10  6:48 Tushar Mulkar
2018-01-10 10:44 ` Tushar Mulkar
2018-01-11 13:54   ` Tushar Mulkar
2018-01-11 14:43     ` Van Haaren, Harry [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=E923DB57A917B54B9182A2E928D00FA650FED9C7@IRSMSX102.ger.corp.intel.com \
    --to=harry.van.haaren@intel.com \
    --cc=tusharmulkar@gmail.com \
    --cc=users@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).