and wait their response.
Signed-off-by: Zhe Tao
---
drivers/net/i40e/i40e_ethdev.c | 169 -
drivers/net/i40e/i40e_ethdev.h | 11 +++
2 files changed, 177 insertions(+), 3 deletions(-)
diff --git a/drivers/net/i40e/i40e_ethdev.c b/drivers/net/i40e
on on this descriptor.
Signed-off-by: Zhe Tao
---
drivers/net/i40e/i40e_rxtx.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/net/i40e/i40e_rxtx.c b/drivers/net/i40e/i40e_rxtx.c
index 2de0ac4..5d33f62 100644
--- a/drivers/net/i40e/i40e_rxtx.c
+++ b/drivers/net
On Fri, Feb 19, 2016 at 01:17:41PM +0800, Wu, Jingjing wrote:
>
>
> > -Original Message-
> > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Zhe Tao
> > Sent: Thursday, January 21, 2016 2:50 PM
> > To: dev at dpdk.org
> > Subject: [dpdk-
Signed-off-by: Zhe Tao
VEB switching feature for i40e is used to enable the switching between the
VSIs connect to the virtual bridge. The old implementation is setting the
virtual bridge mode as VEPA which is port aggregation. Enable the switching
ability by setting the loop back mode for the
both of them. The PF and VMDQ,FD VSIs connect to
the old legacy VEB/VEPA.
All the VEB/VEPA concepts are not specific for FVL, they are defined in the
802.1Qbg spec.
Zhe Tao (2):
support floating VEB config
Add floating VEB support in i40e
doc/guides/rel_notes/release_16_04.rst | 2
Add the new floating related argument option in the EAL.
Using this parameter, all the samples can decide whether to use legacy VEB/VEPA,
or floating VEB.
Even the floating argument is provided in the EAL, but this floating
feature are only support for FVL so far.
Signed-off-by: Zhe Tao
of them. The PF and VMDQ,FD VSIs still connect to
the old legacy VEB/VEPA.
All the VEB/VEPA concepts are not specific for FVL, they are defined in the
802.1Qbg spec.
Signed-off-by: Zhe Tao
---
doc/guides/rel_notes/release_16_04.rst | 2 +
drivers/net/i40e/Makefile | 2 +-
drivers
both of them. The PF and VMDQ,FD VSIs connect to
the old legacy VEB/VEPA.
All the VEB/VEPA concepts are not specific for FVL, they are defined in the
802.1Qbg spec.
Zhe Tao (2):
support floating VEB config
Add floating VEB support in i40e
doc/guides/rel_notes/release_16_04.rst | 2
Add the new floating related argument option in the EAL.
Using this parameter, all the samples can decide whether to use legacy VEB/VEPA,
or floating VEB.
Even the floating argument is provided in the EAL, but this floating
feature are only support for FVL so far.
Signed-off-by: Zhe Tao
of them. The PF and VMDQ,FD VSIs still connect to
the old legacy VEB/VEPA.
All the VEB/VEPA concepts are not specific for FVL, they are defined in the
802.1Qbg spec.
Signed-off-by: Zhe Tao
---
doc/guides/rel_notes/release_16_04.rst | 2 +
drivers/net/i40e/Makefile | 2 +-
drivers
function when secondary process call the init function for eth dev.
Signed-off-by: Zhe Tao
---
drivers/net/ixgbe/ixgbe_ethdev.c | 17 +++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ixgbe/ixgbe_ethdev.c b/drivers/net/ixgbe/ixgbe_ethdev.c
index 3e6fe86
connect to PF
or VFs.
Signed-off-by: Zhe Tao
---
drivers/net/i40e/i40e_ethdev.c | 48 +++---
1 file changed, 40 insertions(+), 8 deletions(-)
diff --git a/drivers/net/i40e/i40e_ethdev.c b/drivers/net/i40e/i40e_ethdev.c
index bf6220d..ba2ba9e 100644
--- a
both of them. The PF and VMDQ,FD VSIs connect to
the old legacy VEB/VEPA.
Zhe Tao (2):
support floating VEB config
Add floating VEB support in i40e
drivers/net/i40e/Makefile | 2 +-
drivers/net/i40e/i40e_ethdev.c | 92 ++
drivers/net
Add the new floating related argument option in the EAL.
using this parameter, all the samples can decide whether to use legacy VEB/VEPA,
or floating VEB.
Signed-off-by: Zhe Tao
---
lib/librte_eal/common/eal_common_options.c | 4
lib/librte_eal/common/eal_internal_cfg.h | 1 +
lib
of them. The PF and VMDQ,FD VSIs connect to
the old legacy VEB/VEPA.
Signed-off-by: Zhe Tao
---
drivers/net/i40e/Makefile | 2 +-
drivers/net/i40e/i40e_ethdev.c | 92 ++
drivers/net/i40e/i40e_ethdev.h | 3 ++
drivers/net/i40e/i40e_pf.c | 10
: add vector Rx")
Signed-off-by: Zhe Tao
---
v2: Changed the comments according to the code change.
v3: Fixed the issues reported by check-git-log.sh.
drivers/net/i40e/i40e_rxtx_vec.c | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/drivers/net/i40e/i40e_rx
of them. The PF and VMDQ,FD VSIs connect to
the old legacy VEB/VEPA.
All the VEB/VEPA concepts are not specific for FVL, they are defined in the
802.1Qbg spec.
This floating VEB only take effects on the specific version F/W which newer
than 5.0.
Zhe Tao (3):
i40e: support floating VEB config
ans
the traffic cannot go to ouside world.
2. doesn't need to connect to the phsical port which means
when the physical link is down the floating VEB can still works
fine.
Signed-off-by: Zhe Tao
---
drivers/net/i40e/i40e_ethdev.c | 44 ++
drivers/net/i40
them. The PF and VMDQ,FD VSIs still connect to
the old legacy VEB/VEPA.
All the VEB/VEPA concepts are not specific for FVL, they are defined in
the 802.1Qbg spec.
Now the floating VEB feature is only avaiable for the FW version which
newer than 5.0 (FW major version number > 5).
Signed-off-by:
loating VEB and one legacy
VEB. VF can connect to floating VEB or legacy VEB according to the
configuration.
Signed-off-by: Zhe Tao
---
doc/guides/nics/i40e.rst | 8 ++
drivers/net/i40e/i40e_ethdev.c | 56 --
drivers/net/i40e/i40e_ethdev.h | 1
On Tue, Jun 14, 2016 at 01:57:11PM +0800, Zhe Tao wrote:
> This patch-set add the support for floating VEB in i40e.
> All the VFs VSIs can decide whether to connect to the legacy VEB/VEPA or
> the floating VEB. When connect to the floating VEB a new floating VEB is
> created. Now all
of them. The PF and VMDQ,FD VSIs connect to
the old legacy VEB/VEPA.
All the VEB/VEPA concepts are not specific for FVL, they are defined in the
802.1Qbg spec.
This floating VEB only take effects on the specific version F/W which newer
than 5.0.
Zhe Tao (2):
i40e: support floating VEB config
the 802.1Qbg spec.
But for floating VEB, it has two major difference.
1. doesn't has a up link connection which means
the traffic cannot go to outside world.
2. doesn't need to connect to the physical port which means
when the physical link is down the floating VEB can still works
fi
ing veb using
"floating_veb_list".
Like "-w 84:00.0,enable_floating_veb=1,floating_veb_list=1/3-4", means VF1, VF3,
VF4 connect to the floating VEB, other VFs connect to the legacy VEB.The "/"
is used for delimiter of the floating VEB list.
Signed-off-by: Zhe Tao
---
d
On Fri, Jun 24, 2016 at 12:14:14PM +0100, Ferruh Yigit wrote:
> Hi Zhe,
>
> On 6/24/2016 9:29 AM, Zhe Tao wrote:
> > Add the new floating VEB related arguments option in the devarg.
> > Using this parameter, all the applications can decide whether to use legacy
> &g
of them. The PF and VMDQ,FD VSIs connect to
the old legacy VEB/VEPA.
All the VEB/VEPA concepts are not specific for FVL, they are defined in the
802.1Qbg spec.
This floating VEB only take effects on the specific version F/W which newer
than 5.0.
Zhe Tao (2):
i40e: support floating VEB config
ard VEB:
1. doesn't has a up link connection which means
the traffic cannot go to outside world.
2. doesn't need to connect to the physical port which means
when the physical link is down the floating VEB can still works
fine.
Signed-off-by: Zhe Tao
---
drivers/net/i40e
them. The PF and VMDQ,FD VSIs still connect to
the old legacy VEB/VEPA.
All the VEB/VEPA concepts are not specific for FVL, they are defined in
the 802.1Qbg spec.
The floating VEB feature is only available for the FW version which
newer than 5.0 (FW major version number > 5).
Signed-off-by:
ard VEB:
1. doesn't has a up link connection which means
the traffic cannot go to outside world.
2. doesn't need to connect to the physical port which means
when the physical link is down the floating VEB can still works
fine.
Signed-off-by: Zhe Tao
---
drivers/net/i40e
of them. The PF and VMDQ,FD VSIs connect to
the old legacy VEB/VEPA.
All the VEB/VEPA concepts are not specific for FVL, they are defined in the
802.1Qbg spec.
This floating VEB only take effects on the specific version F/W which newer
than 5.0.
Zhe Tao (2):
i40e: support floating VEB config
them. The PF and VMDQ,FD VSIs still connect to
the old legacy VEB/VEPA.
All the VEB/VEPA concepts are not specific for FVL, they are defined in
the 802.1Qbg spec.
The floating VEB feature is only available for the FW version which
newer than 5.0 (FW major version number > 5).
Signed-off-by:
of them. The PF and VMDQ,FD VSIs connect to
the old legacy VEB/VEPA.
All the VEB/VEPA concepts are not specific for FVL, they are defined in the
802.1Qbg spec.
This floating VEB only take effects on the specific version F/W which newer
than 5.0.
Zhe Tao (2):
i40e: add floating VEB support
i40e
oating VEB - even when the physical link on the NIC port is down.
VFs VSIs connect either to the standard VEB/VEPA or to the floating VEB,
they cannot connect to both of them. The PF, VMDQ and FD VSIs still
connect to the normal VEB/VEPA.
Signed-off-by: Zhe Tao
---
drivers/net/i40e/i40e_ethd
uires a NIC firmware version
of 5.0 or greater.
Signed-off-by: Zhe Tao
---
doc/guides/nics/i40e.rst | 45 ++
doc/guides/rel_notes/release_16_07.rst | 8 ++
drivers/net/i40e/i40e_ethdev.c | 160 +
drivers/net/i40e/i40e_ethdev.h
of them. The PF and VMDQ,FD VSIs connect to
the old legacy VEB/VEPA.
All the VEB/VEPA concepts are not specific for FVL, they are defined in the
802.1Qbg spec.
This floating VEB only take effects on the specific version F/W.
Zhe Tao (2):
support floating VEB config
Add floating VEB support in
Add the new floating related argument option in the EAL.
Using this parameter, all the samples can decide whether to use legacy VEB/VEPA
or floating VEB.
Even the floating argument is provided in the EAL, but this floating
feature are only support for FVL so far.
Signed-off-by: Zhe Tao
---
doc
them. The PF and VMDQ,FD VSIs still connect to
the old legacy VEB/VEPA.
All the VEB/VEPA concepts are not specific for FVL, they are defined in the
802.1Qbg spec.
Now the floating VEB feature is only avaiable in the specific version of FW.
Signed-off-by: Zhe Tao
---
doc/guides/rel_notes
/cmdline.c b/app/test-pmd/cmdline.c
> index 73298c9..13194c9 100644
> --- a/app/test-pmd/cmdline.c
> +++ b/app/test-pmd/cmdline.c
> @@ -8687,13 +8687,13 @@ cmd_flow_director_mask_parsed(void *parsed_result,
> return;
> }
Acked-by: Zhe Tao
Hi all,
I have a question about why we need the txe->next_id field in the i40e&ixgbe Tx
function?
>From the current implementation, all the txe is initialized and free
>sequentially,
so we don't need this "next_id" field in our TX function, and when we decide the
"last_id" for txe, we assume the t
function when secondary process call the init function for eth dev.
Fixes: abf7275bbaa2918 (ixgbe: move to drivers/net/)
V2:add fixes line
Signed-off-by: Zhe Tao
---
drivers/net/ixgbe/ixgbe_ethdev.c | 17 +++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/drivers
40e/i40e_ethdev_vf.c | 14 +++---
> drivers/net/i40e/i40e_pf.c | 3 +++
> 4 files changed, 16 insertions(+), 7 deletions(-)
>
> --
> 2.5.0
Acked-by: Zhe Tao
the related LFC enable/disable registers.
PMD driver also need to configure the related registers to control
how often to send the pause frame and what the value in the pause frame.
Signed-off-by: Zhe Tao
---
PATCH V1: Add the LFC support for i40e
PATCH v2: move the LFC parameters init to the
the related LFC enable/disable registers.
PMD driver also need to configure the related registers to control
how often to send the pause frame and what the value in the pause frame.
Signed-off-by: Zhe Tao
---
PATCH V1: add the LFC support for i40e
PATCH v2: move the LFC parameters init to the
This patch set add the vector PMD support for FVL.
FVL vPMD works like the way ixgbe does
All the functionality is tested
Zhe Tao (8):
add vector PMD RX for FVL
add vector PMD TX for FVL
add vector PMD scatter RX for FVL
add RX and TX selection function for FVL
edit the comments
The vPMD RX function uses the multi-buffer and SSE instructions to
accelerate the RX speed, but now the pktype cannot be supported by the vPMD RX,
because it will decrease the performance heavily.
Signed-off-by: Zhe Tao
---
config/common_bsdapp | 2 +
config/common_linuxapp
To support the multiple segments in one packets when the received pkts exceed
one buffer size.
Signed-off-by: Zhe Tao
---
drivers/net/i40e/i40e_rxtx.c | 9
drivers/net/i40e/i40e_rxtx.h | 3 ++
drivers/net/i40e/i40e_rxtx_vec.c | 103 +++
3
To support FVL PMD can select which RX and TX function should be used
according to the queue config.
Signed-off-by: Zhe Tao
---
drivers/net/i40e/base/i40e_type.h | 10 +++
drivers/net/i40e/i40e_ethdev.c| 19 +++-
drivers/net/i40e/i40e_ethdev_vf.c | 27 --
drivers/net/i40e/i40e_rxtx.c
edit the comments for the minimum packets support for vector RX
Signed-off-by: Zhe Tao
---
drivers/net/i40e/i40e_rxtx_vec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/i40e/i40e_rxtx_vec.c b/drivers/net/i40e/i40e_rxtx_vec.c
index b2993e9..6f89002 100644
--- a
according to ixgbe vector implementation, change the data prefetch position
Signed-off-by: Zhe Tao
---
drivers/net/i40e/i40e_rxtx_vec.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/net/i40e/i40e_rxtx_vec.c b/drivers/net/i40e/i40e_rxtx_vec.c
index
update the release note
Signed-off-by: Zhe Tao
---
doc/guides/rel_notes/release_2_2.rst | 4
1 file changed, 4 insertions(+)
diff --git a/doc/guides/rel_notes/release_2_2.rst
b/doc/guides/rel_notes/release_2_2.rst
index bc9b00f..c78ceca 100644
--- a/doc/guides/rel_notes/release_2_2.rst
move all the exta definition out of share code
Signed-off-by: Zhe Tao
---
drivers/net/i40e/base/i40e_type.h | 13 -
drivers/net/i40e/i40e_ethdev.c| 11 ++-
drivers/net/i40e/i40e_ethdev.h| 6 ++
drivers/net/i40e/i40e_ethdev_vf.c | 11 ++-
drivers/net/i40e
The way to increase the performance of the vPMD TX is to use some fast mbuf
release method compares to the scalar TX.
Signed-off-by: Zhe Tao
---
drivers/net/i40e/i40e_rxtx.c | 8 ++
drivers/net/i40e/i40e_rxtx.h | 3 +
drivers/net/i40e/i40e_rxtx_vec.c | 162
update the release note
PATCH v3: make the new patch set
Zhe Tao (4):
add vector PMD RX for FVL
add vector PMD TX for FVL
add vector PMD scatter RX for FVL
add RX and TX selection function for FVL
config/common_bsdapp | 2 +
config/common_linuxapp | 2
The vPMD RX function uses the multi-buffer and SSE instructions to
accelerate the RX speed, but now the pktype cannot be supported by the vPMD RX,
because it will decrease the performance heavily.
Signed-off-by: Zhe Tao
---
config/common_bsdapp | 2 +
config/common_linuxapp
To support the multiple segments in one packets when the received pkts exceed
one buffer size.
Signed-off-by: Zhe Tao
---
drivers/net/i40e/i40e_rxtx.c | 9
drivers/net/i40e/i40e_rxtx.h | 3 ++
drivers/net/i40e/i40e_rxtx_vec.c | 103 +++
3
The way to increase the performance of the vPMD TX is to use some fast mbuf
release method compares to the scalar TX.
Signed-off-by: Zhe Tao
---
drivers/net/i40e/i40e_rxtx.c | 8 ++
drivers/net/i40e/i40e_rxtx.h | 3 +
drivers/net/i40e/i40e_rxtx_vec.c | 162
To support FVL PMD can select which RX and TX function should be used
according to the queue config.
Signed-off-by: Zhe Tao
---
doc/guides/rel_notes/release_2_2.rst | 4 +
drivers/net/i40e/i40e_ethdev.c | 20 +++-
drivers/net/i40e/i40e_ethdev.h | 6 ++
drivers/net/i40e
The vPMD RX function uses the multi-buffer and SSE instructions to
accelerate the RX speed, but now the pktype cannot be supported by the vPMD RX,
because it will decrease the performance heavily.
Signed-off-by: Zhe Tao
---
config/common_bsdapp | 2 +
config/common_linuxapp
The way to increase the performance of the vPMD TX is to use some fast mbuf
release method compares to the scalar TX.
Signed-off-by: Zhe Tao
---
drivers/net/i40e/i40e_rxtx.c | 8 ++
drivers/net/i40e/i40e_rxtx.h | 3 +
drivers/net/i40e/i40e_rxtx_vec.c | 163
To support FVL PMD can select which RX and TX function should be used
according to the queue config.
Signed-off-by: Zhe Tao
---
doc/guides/rel_notes/release_2_2.rst | 4 +
drivers/net/i40e/i40e_ethdev.c | 20 +++-
drivers/net/i40e/i40e_ethdev.h | 6 ++
drivers/net/i40e
To support the multiple segments in one packets when the received pkts exceed
one buffer size.
Signed-off-by: Zhe Tao
---
drivers/net/i40e/i40e_rxtx.c | 9 +++
drivers/net/i40e/i40e_rxtx.h | 3 +
drivers/net/i40e/i40e_rxtx_vec.c | 118 ---
3
update the release note
PATCH v3: make the new patch set
PATCH v4: fix some format issues
Zhe Tao (4):
add vector PMD RX for FVL
add vector PMD TX for FVL
add vector PMD scatter RX for FVL
add RX and TX selection function for FVL
config/common_bsdapp | 2 +
config
Free the memory allocated by the backtrace_symbols
to prevent the memory leak
Signed-off-by: Zhe Tao
---
lib/librte_eal/bsdapp/eal/eal_debug.c | 6 ++
lib/librte_eal/linuxapp/eal/eal_debug.c | 6 ++
2 files changed, 12 insertions(+)
diff --git a/lib/librte_eal/bsdapp/eal/eal_debug.c
("i40e: VXLAN Tx checksum offload")
Signed-off-by: Zhe Tao
---
app/test-pmd/csumonly.c | 26 +++---
drivers/net/i40e/i40e_rxtx.c | 10 --
lib/librte_mbuf/rte_mbuf.h | 11 +++
3 files changed, 38 insertions(+), 9 deletions(-)
diff --git a/ap
VXLAN Tx checksum offload")
Signed-off-by: Zhe Tao
---
V2: Edited some comments for mbuf structure and i40e driver.
app/test-pmd/csumonly.c | 26 +++---
drivers/net/i40e/i40e_rxtx.c | 12 +---
lib/librte_mbuf/rte_mbuf.h | 16 +++-
3 files c
On Thu, Jul 07, 2016 at 08:24:43PM +0800, Ananyev, Konstantin wrote:
>
>
> > -Original Message-
> > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Ananyev, Konstantin
> > Sent: Thursday, July 07, 2016 11:51 AM
> > To: Tao, Zhe; dev at dpdk.org
> > Cc: Tao, Zhe; Wu, Jingjing
> > S
AN Tx checksum offload")
Signed-off-by: Zhe Tao
---
v2: edited the comments
v3: added external IP offload flag when TSO is enabled for tunnelling packets
app/test-pmd/csumonly.c | 29 +
drivers/net/i40e/i40e_rxtx.c | 12 +---
lib/librte_mbuf/rte_mbu
| 3 +++
> doc/guides/rel_notes/release_16_07.rst | 2 ++
> drivers/net/i40e/i40e_rxtx.c | 27 +++
> lib/librte_mbuf/rte_mbuf.h | 7 +++
> 4 files changed, 39 insertions(+)
>
> --
> 2.4.0
Acked-by: Zhe Tao
I40E_PRTQF_FLX_PIT_DEST_OFF_SHIFT) & \
> I40E_PRTQF_FLX_PIT_DEST_OFF_MASK))
>
> --
> 2.4.0
Acked-by: Zhe Tao
From: "zhe.tao"
If the PF link is down and up, VF link will not work
accordingly.
This patch set addes the support of VF link reset. So, when VF
receices the messges of physical link down/up. APP can reset the
VF link and let it recover.
PS: This patch set is splitted from a previous patch set,
From: Wenzhuo Lu
Add an API to reset the device.
It's for VF device in this scenario, kernel PF + DPDK VF.
When the PF port down/up, APP should call this API to
reset VF port. Most likely, APP should call it in its
management thread and guarantee the thread safe.
Signed-off-by: Wenzhuo Lu
Signe
.
Signed-off-by: Wenzhuo Lu
Signed-off-by: Zhe Tao
Signed-off-by: zhe.tao
---
lib/librte_ether/rte_ethdev.h | 62 +++
1 file changed, 62 insertions(+)
diff --git a/lib/librte_ether/rte_ethdev.h b/lib/librte_ether/rte_ethdev.h
index 74e895f..4efb5e9 100644
From: Wenzhuo Lu
Add RX/TX paths with lock for VF. It's used when
the function of link reset on VF is needed.
When the lock for RX/TX is added, the RX/TX can be
stopped. Then we have a chance to reset the VF link.
Please be aware there's performence drop if the lock
path is chosen.
Signed-off-b
From: Wenzhuo Lu
Implement the device reset function.
1, Add the fake RX/TX functions.
2, The reset function tries to stop RX/TX by replacing
the RX/TX functions with the fake ones and getting the
locks to make sure the regular RX/TX finished.
3, After the RX/TX stopped, reset the VF port,
From: Wenzhuo Lu
Add RX/TX paths with lock for VF. It's used when
the function of link reset on VF is needed.
When the lock for RX/TX is added, the RX/TX can be
stopped. Then we have a chance to reset the VF link.
Please be aware there's performence drop if the lock
path is chosen.
Signed-off-b
From: Wenzhuo Lu
Implement the device reset function.
1, Add the fake RX/TX functions.
2, The reset function tries to stop RX/TX by replacing
the RX/TX functions with the fake ones and getting the
locks to make sure the regular RX/TX finished.
3, After the RX/TX stopped, reset the VF port,
From: "zhe.tao"
Implement the device reset function.
1, Add the fake RX/TX functions.
2, The reset function tries to stop RX/TX by replacing
the RX/TX functions with the fake ones and getting the
locks to make sure the regular RX/TX finished.
3, After the RX/TX stopped, reset the VF port, a
From: "zhe.tao"
Add RX/TX paths with lock for VF. It's used when
the function of link reset on VF is needed.
When the lock for RX/TX is added, the RX/TX can be
stopped. Then we have a chance to reset the VF link.
Please be aware there's performence drop if the lock
path is chosen.
Signed-off-by
ck on VF
igb: implement device reset on VF
Zhe Tao (2):
i40e: RX/TX with lock on VF
i40e: implement device reset on VF
v1:
Added the implementation for the VF reset functionality.
v2:
Changed the i40e related operations during VF reset.
v3:
Resent the patches because of the mail
: Wenzhuo Lu
Signed-off-by: Zhe Tao
---
lib/librte_ether/rte_ethdev.h | 62 +++
1 file changed, 62 insertions(+)
diff --git a/lib/librte_ether/rte_ethdev.h b/lib/librte_ether/rte_ethdev.h
index 74e895f..4efb5e9 100644
--- a/lib/librte_ether/rte_ethdev.h
+++ b
Add an API to reset the device.
It's for VF device in this scenario, kernel PF + DPDK VF.
When the PF port down/up, APP should call this API to
reset VF port. Most likely, APP should call it in its
management thread and guarantee the thread safe.
Signed-off-by: Wenzhuo Lu
---
lib/librte_ether/rt
Add RX/TX paths with lock for VF. It's used when
the function of link reset on VF is needed.
When the lock for RX/TX is added, the RX/TX can be
stopped. Then we have a chance to reset the VF link.
Please be aware there's performence drop if the lock
path is chosen.
Signed-off-by: Wenzhuo Lu
---
Implement the device reset function.
1, Add the fake RX/TX functions.
2, The reset function tries to stop RX/TX by replacing
the RX/TX functions with the fake ones and getting the
locks to make sure the regular RX/TX finished.
3, After the RX/TX stopped, reset the VF port, and then
release
Add RX/TX paths with lock for VF. It's used when
the function of link reset on VF is needed.
When the lock for RX/TX is added, the RX/TX can be
stopped. Then we have a chance to reset the VF link.
Please be aware there's performence drop if the lock
path is chosen.
Signed-off-by: Wenzhuo Lu
---
Implement the device reset function.
1, Add the fake RX/TX functions.
2, The reset function tries to stop RX/TX by replacing
the RX/TX functions with the fake ones and getting the
locks to make sure the regular RX/TX finished.
3, After the RX/TX stopped, reset the VF port, and then
release
Add RX/TX paths with lock for VF. It's used when
the function of link reset on VF is needed.
When the lock for RX/TX is added, the RX/TX can be
stopped. Then we have a chance to reset the VF link.
Please be aware there's performence drop if the lock
path is chosen.
Signed-off-b
release the locks.
Signed-off-by: Zhe Tao
---
app/test-pmd/config.c | 3 +
doc/guides/rel_notes/release_16_07.rst | 5 ++
drivers/net/i40e/i40e_ethdev.h | 7 +-
drivers/net/i40e/i40e_ethdev_vf.c | 152 -
drivers/net/i40e/i40e_rxtx.c
ck on VF
igb: implement device reset on VF
Zhe Tao (2):
i40e: RX/TX with lock on VF
i40e: implement device reset on VF
v1:
Added the implementation for the VF reset functionality.
v2:
Changed the i40e related operations during VF reset.
v3:
Resent the patches because of the mail
: Wenzhuo Lu
Signed-off-by: Zhe Tao
---
lib/librte_ether/rte_ethdev.h | 62 +++
1 file changed, 62 insertions(+)
diff --git a/lib/librte_ether/rte_ethdev.h b/lib/librte_ether/rte_ethdev.h
index 74e895f..4efb5e9 100644
--- a/lib/librte_ether/rte_ethdev.h
+++ b
Add an API to reset the device.
It's for VF device in this scenario, kernel PF + DPDK VF.
When the PF port down/up, APP should call this API to
reset VF port. Most likely, APP should call it in its
management thread and guarantee the thread safe.
Signed-off-by: Wenzhuo Lu
---
lib/librte_ether/rt
Add RX/TX paths with lock for VF. It's used when
the function of link reset on VF is needed.
When the lock for RX/TX is added, the RX/TX can be
stopped. Then we have a chance to reset the VF link.
Please be aware there's performence drop if the lock
path is chosen.
Signed-off-by: Wenzhuo Lu
---
Implement the device reset function.
1, Add the fake RX/TX functions.
2, The reset function tries to stop RX/TX by replacing
the RX/TX functions with the fake ones and getting the
locks to make sure the regular RX/TX finished.
3, After the RX/TX stopped, reset the VF port, and then
release
Add RX/TX paths with lock for VF. It's used when
the function of link reset on VF is needed.
When the lock for RX/TX is added, the RX/TX can be
stopped. Then we have a chance to reset the VF link.
Please be aware there's performence drop if the lock
path is chosen.
Signed-off-by: Wenzhuo Lu
---
Implement the device reset function.
1, Add the fake RX/TX functions.
2, The reset function tries to stop RX/TX by replacing
the RX/TX functions with the fake ones and getting the
locks to make sure the regular RX/TX finished.
3, After the RX/TX stopped, reset the VF port, and then
release
Add RX/TX paths with lock for VF. It's used when
the function of link reset on VF is needed.
When the lock for RX/TX is added, the RX/TX can be
stopped. Then we have a chance to reset the VF link.
Please be aware there's performence drop if the lock
path is chosen.
Signed-off-b
release the locks.
Signed-off-by: Zhe Tao
---
doc/guides/rel_notes/release_16_07.rst | 5 ++
drivers/net/i40e/i40e_ethdev.h | 7 +-
drivers/net/i40e/i40e_ethdev_vf.c | 152 -
drivers/net/i40e/i40e_rxtx.c | 10 +++
drivers/net/i40e/i40e_rxtx.h
)
Signed-off-by: Zhe Tao
---
v2: Changed the comments according to the code change.
drivers/net/i40e/i40e_rxtx_vec.c | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/drivers/net/i40e/i40e_rxtx_vec.c b/drivers/net/i40e/i40e_rxtx_vec.c
index eef80d9..dd113f3 100644
them. The PF and VMDQ,FD VSIs still connect to
the old legacy VEB/VEPA.
All the VEB/VEPA concepts are not specific for FVL, they are defined in the
802.1Qbg spec.
Now the floating VEB feature is only avaiable for the FW version which
newer than 5.0 (FW major version number > 5).
Signed-off-by:
ans
the traffic cannot go to ouside world.
2. doesn't need to connect to the phsical port which means
when the physical link is down the floating VEB can still works
fine.
Signed-off-by: Zhe Tao
---
drivers/net/i40e/i40e_ethdev.c | 44 ++
drivers/ne
of them. The PF and VMDQ,FD VSIs connect to
the old legacy VEB/VEPA.
All the VEB/VEPA concepts are not specific for FVL, they are defined in the
802.1Qbg spec.
This floating VEB only take effects on the specific version F/W which newer
than 5.0.
Zhe Tao (3):
Support floating VEB config
Add
1 - 100 of 154 matches
Mail list logo
