[dpdk-dev] [PATCH v5 0/2] fm10k: enable FTAG based forwarding
On Wed, Mar 02, 2016 at 07:19:12PM +0800, Wang Xiao W wrote: > v5: > * Used kvargs api to parse the devargs parameter. > * Put release note into the driver patch. > > v4: > * Removed the build time config option, used devargs to config FTAG. > * Rebased on head of dpdk-next-net/rel_16_04 branch. > > v3: > * Removed "\n" in PMD_INIT_LOG. > * Returned "-ENOTSUP" instead of -1 in VF FTAG use case. > > v2: > * Gave an error message for VF FTAG use case. > * Added a notice in the doc to emphasize that application should ensure > an appropriate FTAG for every frame in FTAG based forwarding mode. > > Wang Xiao W (2): > fm10k: enable FTAG based forwarding > doc: add introduction for fm10k FTAG based forwarding > Applied to dpdk-next-net/rel_16_04 /Bruce
[dpdk-dev] [PATCH v5 0/2] fm10k: enable FTAG based forwarding
Hi, We reached a consensus on configuring FTAG by devargs method, any other suggestion or concern for this patch? Best Regards, Xiao > -Original Message- > From: Liu, Yong > Sent: Tuesday, March 8, 2016 3:58 PM > To: Wang, Xiao W ; Chen, Jing D > > Cc: dev at dpdk.org > Subject: RE: [dpdk-dev] [PATCH v5 0/2] fm10k: enable FTAG based forwarding > > Tested-by: Yong Liu > > - Tested Branch: dpdk-next-net/rel_16_04 > - Tested Commit: 4ac366ba647909c3b71818f9be9db86ba5e871da > - OS: Fedora20 3.11.10-301.fc20.x86_64 > - GCC: gcc version 4.8.3 20140911 > - CPU: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz > - NIC: Intel Corporation Device RedrockCanyou [8086:15a4] > - Default x86_64-native-linuxapp-gcc configuration > - Prerequisites: > - Total 1 cases, 1 passed, 0 failed > > - Prerequisites command / instruction: > Apply fm_ftag unit test patch. > export Port0 and Port1's GLORT ID to environment variables > export PORT1_GLORT=0x4200 > export PORT0_GLORT=0x4000 > > - Case: Ftag forwarding unit test > Description: check fm10k nic can forwarding packets based on FTAG > Command / instruction: > Start test application and run fm10k_ftag_autotest > test -c f -n 4 -w 83:00.0,enable_ftag=1 -w 85:00.0,enable_ftag=1 > RTE>>fm10k_ftag_autotest > Send packet to Port0 and verify packet forwarded to Port1 > Receive 1 packets on port 0 > test for FTAG RX passed > Send out 1 packets with FTAG on port 0 > Receive 1 packets on port 1 > test for FTAG TX passed > Test OK > > > > -Original Message- > > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Wang Xiao W > > Sent: Wednesday, March 02, 2016 7:19 PM > > To: Chen, Jing D > > Cc: dev at dpdk.org > > Subject: [dpdk-dev] [PATCH v5 0/2] fm10k: enable FTAG based forwarding > > > > v5: > > * Used kvargs api to parse the devargs parameter. > > * Put release note into the driver patch. > > > > v4: > > * Removed the build time config option, used devargs to config FTAG. > > * Rebased on head of dpdk-next-net/rel_16_04 branch. > > > > v3: > > * Removed "\n" in PMD_INIT_LOG. > > * Returned "-ENOTSUP" instead of -1 in VF FTAG use case. > > > > v2: > > * Gave an error message for VF FTAG use case. > > * Added a notice in the doc to emphasize that application should ensure > > an appropriate FTAG for every frame in FTAG based forwarding mode. > > > > Wang Xiao W (2): > > fm10k: enable FTAG based forwarding > > doc: add introduction for fm10k FTAG based forwarding > > > > doc/guides/nics/fm10k.rst | 16 - > > doc/guides/rel_notes/release_16_04.rst | 2 ++ > > drivers/net/fm10k/fm10k.h | 2 ++ > > drivers/net/fm10k/fm10k_ethdev.c | 65 > > +- > > drivers/net/fm10k/fm10k_rxtx.c | 15 > > drivers/net/fm10k/fm10k_rxtx_vec.c | 3 ++ > > 6 files changed, 101 insertions(+), 2 deletions(-) > > > > -- > > 1.9.3
[dpdk-dev] [PATCH v5 0/2] fm10k: enable FTAG based forwarding
Tested-by: Yong Liu - Tested Branch: dpdk-next-net/rel_16_04 - Tested Commit: 4ac366ba647909c3b71818f9be9db86ba5e871da - OS: Fedora20 3.11.10-301.fc20.x86_64 - GCC: gcc version 4.8.3 20140911 - CPU: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz - NIC: Intel Corporation Device RedrockCanyou [8086:15a4] - Default x86_64-native-linuxapp-gcc configuration - Prerequisites: - Total 1 cases, 1 passed, 0 failed - Prerequisites command / instruction: Apply fm_ftag unit test patch. export Port0 and Port1's GLORT ID to environment variables export PORT1_GLORT=0x4200 export PORT0_GLORT=0x4000 - Case: Ftag forwarding unit test Description: check fm10k nic can forwarding packets based on FTAG Command / instruction: Start test application and run fm10k_ftag_autotest test -c f -n 4 -w 83:00.0,enable_ftag=1 -w 85:00.0,enable_ftag=1 RTE>>fm10k_ftag_autotest Send packet to Port0 and verify packet forwarded to Port1 Receive 1 packets on port 0 test for FTAG RX passed Send out 1 packets with FTAG on port 0 Receive 1 packets on port 1 test for FTAG TX passed Test OK > -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Wang Xiao W > Sent: Wednesday, March 02, 2016 7:19 PM > To: Chen, Jing D > Cc: dev at dpdk.org > Subject: [dpdk-dev] [PATCH v5 0/2] fm10k: enable FTAG based forwarding > > v5: > * Used kvargs api to parse the devargs parameter. > * Put release note into the driver patch. > > v4: > * Removed the build time config option, used devargs to config FTAG. > * Rebased on head of dpdk-next-net/rel_16_04 branch. > > v3: > * Removed "\n" in PMD_INIT_LOG. > * Returned "-ENOTSUP" instead of -1 in VF FTAG use case. > > v2: > * Gave an error message for VF FTAG use case. > * Added a notice in the doc to emphasize that application should ensure > an appropriate FTAG for every frame in FTAG based forwarding mode. > > Wang Xiao W (2): > fm10k: enable FTAG based forwarding > doc: add introduction for fm10k FTAG based forwarding > > doc/guides/nics/fm10k.rst | 16 - > doc/guides/rel_notes/release_16_04.rst | 2 ++ > drivers/net/fm10k/fm10k.h | 2 ++ > drivers/net/fm10k/fm10k_ethdev.c | 65 > +- > drivers/net/fm10k/fm10k_rxtx.c | 15 > drivers/net/fm10k/fm10k_rxtx_vec.c | 3 ++ > 6 files changed, 101 insertions(+), 2 deletions(-) > > -- > 1.9.3
[dpdk-dev] [PATCH v5 0/2] fm10k: enable FTAG based forwarding
v5: * Used kvargs api to parse the devargs parameter. * Put release note into the driver patch. v4: * Removed the build time config option, used devargs to config FTAG. * Rebased on head of dpdk-next-net/rel_16_04 branch. v3: * Removed "\n" in PMD_INIT_LOG. * Returned "-ENOTSUP" instead of -1 in VF FTAG use case. v2: * Gave an error message for VF FTAG use case. * Added a notice in the doc to emphasize that application should ensure an appropriate FTAG for every frame in FTAG based forwarding mode. Wang Xiao W (2): fm10k: enable FTAG based forwarding doc: add introduction for fm10k FTAG based forwarding doc/guides/nics/fm10k.rst | 16 - doc/guides/rel_notes/release_16_04.rst | 2 ++ drivers/net/fm10k/fm10k.h | 2 ++ drivers/net/fm10k/fm10k_ethdev.c | 65 +- drivers/net/fm10k/fm10k_rxtx.c | 15 drivers/net/fm10k/fm10k_rxtx_vec.c | 3 ++ 6 files changed, 101 insertions(+), 2 deletions(-) -- 1.9.3
