From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Nemeth, Balazs" <balazs.nemeth@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] ixgbe_vf: Fix getting link state
Date: Fri, 19 Dec 2014 23:42:06 +0100 [thread overview]
Message-ID: <2115719.IJ2O6rpKyu@xps13> (raw)
In-Reply-To: <91383E96CE459D47BCE92EFBF5CE73B004F1CDCC@IRSMSX108.ger.corp.intel.com>
> > This patch fixes checking the link state of a virtual function. If the state has
> > already been checked, it does not need to be checked again. Previously,
> > get_link_status in the ixgbe_hw struct was used to track if the information
> > had already been retrieved, but this field was always set to false (signifying
> > that the information was up-to-date). The problem was introduced by
> > commit 8ef32003 which was part of a patch set to update the ixgbe portion of
> > the PMD. This patch does not break consistency with the ixgbevf driver.
> > Instead, it fixes the problem at the level of DPDK.
> >
> > Applications that rely on the reported link speed could fail without this patch.
> > The qos_sched example application provided with DPDK did not run when
> > virtual functions were used. The output for this example application is shown
> > below:
> >
> > EAL: Error - exiting with code: 1
> > Cause: Unable to config sched subport 0, err=-2
> >
> > The problem and the effect of the patch can been seen by running the l2fwd
> > example application using the following command:
> >
> > sudo ./build/l2fwd -c 0x3 -n 4 -- -p 0x3 -T 0
> >
> > Before the patch has been applied (with both links up):
> > ...
> > Checking link statusdone
> > Port 0 Link Up - speed 100 Mbps - half-duplex
> >
> > Port 1 Link Up - speed 100 Mbps - half-duplex
> >
> > L2FWD: entering main loop on lcore 1
> > ...
> >
> > After the patch has been applied (with both links up):
> > ...
> > Checking link statusdone
> > Port 0 Link Up - speed 10000 Mbps - full-duplex Port 1 Link Up - speed 10000
> > Mbps - full-duplex
> > L2FWD: entering main loop on lcore 1
> > ...
> >
> > Before the patch has been applied (with link 0 down, link 1 up):
> > ...
> > Checking link statusdone
> > Port 0 Link Up - speed 100 Mbps - half-duplex
> >
> > Port 1 Link Up - speed 100 Mbps - half-duplex
> >
> > L2FWD: entering main loop on lcore 1
> > ...
> >
> > After the patch has been applied (with link 0 down, link 1 up):
> > ...
> > Checking link status............................................................
> > ..............................done
> > Port 0 Link Down
> > Port 1 Link Up - speed 10000 Mbps - full-duplex ...
> >
> > Signed-off-by: Balazs Nemeth <balazs.nemeth@intel.com>
> > ---
> >
> > changes v2:
> > * Include more elaborate explanation of the problem in the commit message
> > * Fix the issue at the level of DPDK not touching ixgbe driver code
> >
> > lib/librte_pmd_ixgbe/ixgbe_ethdev.c | 10 +++++++++-
> > 1 file changed, 9 insertions(+), 1 deletion(-)
>
> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
Applied
Thanks
--
Thomas
prev parent reply other threads:[~2014-12-19 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 13:22 [dpdk-dev] [PATCH] " Balazs Nemeth
2014-12-17 13:24 ` Thomas Monjalon
2014-12-18 4:20 ` Choonho Son
2014-12-18 17:56 ` [dpdk-dev] [PATCH v2] " Balazs Nemeth
2014-12-19 15:34 ` Gonzalez Monroy, Sergio
2014-12-19 22:42 ` Thomas Monjalon [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=2115719.IJ2O6rpKyu@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=balazs.nemeth@intel.com \
--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 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).