It seems compilation for clang Linux target is broken:
In file included from
/home/marc/dpdk/lib/librte_eal/linuxapp/eal/eal_pci.c:42:
/home/marc/dpdk/x86_64-native-linuxapp-clang/include/rte_memcpy.h:870:2:
error: implicit declaration of function '_mm_alignr_epi8' is invalid in C99
Add new features, ABI changes and resolved issues notice for
the refactored link patch.
Signed-off-by: Marc Sune
---
doc/guides/rel_notes/release_2_3.rst | 102 +++
1 file changed, 102 insertions(+)
create mode 100644 doc/guides/rel_notes/release_2_3.rst
diff
This patch redesigns the API to set the link speed/s configure
for an ethernet port. Specifically:
- it allows to define a set of advertised speeds for
auto-negociation.
- it allows to disable link auto-negociation (single fixed speed).
- default: auto-negociate all supported speeds.
Other
Added constants and bitmap to struct rte_eth_dev_info to be used by PMDs.
Signed-off-by: Marc Sune
---
lib/librte_ether/rte_ethdev.h | 24
1 file changed, 24 insertions(+)
diff --git a/lib/librte_ether/rte_ethdev.h b/lib/librte_ether/rte_ethdev.h
index 16da821..83ddbb7
The current rte_eth_dev_info abstraction does not provide any mechanism to
get the supported speed(s) of an ethdev.
For some drivers (e.g. ixgbe), an educated guess could be done based on the
driver's name (driver_name in rte_eth_dev_info), see:
Signed-off-by: Wenzhuo Lu
---
drivers/net/ixgbe/base/README | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ixgbe/base/README b/drivers/net/ixgbe/base/README
index 5d66f86..caa2664 100644
--- a/drivers/net/ixgbe/base/README
+++ b/drivers/net/ixgbe/base/README
@@
The MDIO clock speed must be reconfigured after the MAC reset.
The MDIO clock speed becomes invalid, therefore the driver reads
invalid PHY register values. The driver now set the MDIO clock
speed prior to initializing PHY ops and again after the MAC reset.
As now the MDIO speed gets set in more
Do not set FDIRCTRL.DROP_NO_MATCH in ixgbe_init_fdir_perfect_82599(),
this bit is already set in ixgbe_set_fdir_drop_queue_82599() which
makes more sense for drivers that call that function.
This resolves an issue where packets were being dropped when switching
to perfect filters mode.
Setting
Instead of not defining the callback for set_phy_power when
manageability is enabled, put the check in the set_phy_power
function so that only turning the power off is conditional on
management, but not turning the PHY on.
Signed-off-by: Wenzhuo Lu
---
drivers/net/ixgbe/base/ixgbe_phy.c | 3
This patch resolves an issue where VF mac address is zeroed out
in cases where the VF driver is loaded while the PF interface
is down.
The solution is to only set it when we get an ACK from the PF.
Fixes: 6202266e5680 ("ixgbe/base: vf changes")
Signed-off-by: Wenzhuo Lu
---
Use the PHY token, shared between sw-fw for PHY access on X550EM_a.
Signed-off-by: Wenzhuo Lu
---
doc/guides/rel_notes/release_16_04.rst | 5 ++
drivers/net/ixgbe/base/ixgbe_x550.c| 114 +
drivers/net/ixgbe/base/ixgbe_x550.h| 2 +
3 files changed, 121
Add new X550EM_a devices and their mac types, X550EM_a
and X550EM_a_vf.
Update the code to use the new devices and mac types.
Signed-off-by: Wenzhuo Lu
---
doc/guides/rel_notes/release_16_04.rst | 5 ++
drivers/net/ixgbe/base/ixgbe_82599.c | 4 +-
drivers/net/ixgbe/base/ixgbe_api.c | 23
*add x550em_a device support
*add x550em_x V2 device support
*sw-firmware sync for resource sharing
*set VF mac addr only when acked by PF
*ignore manageability for phy power on
*add register definition for SGMII busy
*fix setting flow dir flag twice
*set MDIO speed after MAC reset
*abstract out
Add multicast promiscuous mode support on ixgbe VF driver.
Please note if we want to use this promiscuous mode, we need both PF
and VF driver to support it. The reason is this VF feature is
configged on PF.
If use kernel PF driver + dpdk VF driver, make sure kernel PF driver
support VF multicast
On Sat, 13 Feb 2016 17:43:38 +
"Wiles, Keith" wrote:
> The reason it appears to just exit to the shell is I was setting ?log-level 0
> on the command line, which means no CRIT, EMERG or ALERTs panic messages are
> printed. If I set the log-level 3 then I am able to see these ?critical?
>
On Fri, 12 Feb 2016 22:41:18 -0800
Matthew Hall wrote:
> Signed-off-by: Matthew Hall
> ---
> lib/librte_eal/linuxapp/eal/eal_interrupts.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/lib/librte_eal/linuxapp/eal/eal_interrupts.c
> b/lib/librte_eal/linuxapp/eal/eal_interrupts.c
>
> -Original Message-
> From: David Marchand [mailto:david.marchand at 6wind.com]
> Sent: Wednesday, January 27, 2016 4:34 PM
> To: Wu, Jingjing
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2 2/2] i40evf: support interrupt based pf
> reset request
>
> Hello Jingjing,
>
> On
> -Original Message-
> From: Tao, Zhe
> Sent: Friday, January 29, 2016 4:51 PM
> To: Wu, Jingjing; dev at dpdk.org
> Subject: RE: [dpdk-dev] [PATCH v2 2/2] i40evf: support interrupt based pf
> reset request
>
>
>
> > -Original Message-
> > From: dev [mailto:dev-bounces at
> -Original Message-
> From: Tao, Zhe
> Sent: Friday, January 29, 2016 3:28 PM
> To: Wu, Jingjing; dev at dpdk.org
> Subject: RE: [dpdk-dev] [PATCH v2 1/2] i40evf: allocate virtchnl cmd buffer
> for each vf
>
>
>
> > -Original Message-
> > From: dev [mailto:dev-bounces at
> -Original Message-
> From: Tao, Zhe
> Sent: Thursday, January 28, 2016 3:03 PM
> To: Wu, Jingjing
> Cc: dev at dpdk.org
> Subject: RE: [dpdk-dev] [PATCH v2 2/2] i40evf: support interrupt based pf
> reset request
>
> > @@ -74,8 +74,6 @@
> > +static void
> > @@ -1662,7 +1869,8 @@
Hi Bruce,
Best regards
Wenzhuo Lu
> -Original Message-
> From: Richardson, Bruce
> Sent: Monday, February 8, 2016 10:02 PM
> To: Lu, Wenzhuo
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] ixgbe: support multicast promiscuous mode on
> VF
>
> On Mon, Jan 04, 2016 at 04:07:16PM
21 matches
Mail list logo
