All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 461] i40evf link status is always down with the Intel XL710 driver
Date: Fri, 24 Apr 2020 03:17:57 +0000	[thread overview]
Message-ID: <bug-461-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=461

            Bug ID: 461
           Summary: i40evf link status is always down with the Intel XL710
                    driver
           Product: DPDK
           Version: 20.02
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: critical
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: li_hong.bi@nokia-sbell.com
  Target Milestone: ---

When host uses i40e-2.10.19.82 driver for XL710 nic , in container the link
status is always down when XL710 VF nic uses dpdk i40evf pmd driver.

from code analysis, i40e-2.10.19.82 driver will convert link speed type
(I40E_LINK_SPEED_XXX) to mbs type (SPEED_XXX), but i40evf_dev_link_update()
only support I40E_LINK_SPEED_XXX and regard SPEED_XXX as invalid type.

        default:
                new_link.link_speed = ETH_SPEED_NUM_NONE;
                break;
        }
        /* full duplex only */
        new_link.link_duplex = ETH_LINK_FULL_DUPLEX;
        new_link.link_status = vf->link_up &&
                                new_link.link_speed != ETH_SPEED_NUM_NONE
                                ? ETH_LINK_UP
                                : ETH_LINK_DOWN;

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2020-04-24  3:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-461-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.