> -Original Message-
> From: Adrien Mazarguil [mailto:adrien.mazarg...@6wind.com]
> Sent: Friday, December 23, 2016 4:43 PM
> To: Xing, Beilei
> Cc: Yigit, Ferruh ; Wu, Jingjing
> ; Zhang, Helin ;
> dev@dpdk.org; Lu, Wenzhuo
> Subject: Re: [dpdk-dev] [PATCH 10/24] ethdev: parse ethertyp
This patch adds i40e_ethertype_filter_flush function
to flush all ethertype filters, including filters in
SW and HW.
Signed-off-by: Beilei Xing
---
drivers/net/i40e/i40e_flow.c | 36
1 file changed, 36 insertions(+)
diff --git a/drivers/net/i40e/i40e_flow.c
This patch adds i40e_tunnel_filter_flush function
to flush all tunnel filters, including filters in
SW and HW.
Signed-off-by: Beilei Xing
---
drivers/net/i40e/i40e_flow.c | 36
1 file changed, 36 insertions(+)
diff --git a/drivers/net/i40e/i40e_flow.c b/driv
This patch supports destroying a flow directory filter
for users.
Signed-off-by: Beilei Xing
---
drivers/net/i40e/i40e_flow.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/net/i40e/i40e_flow.c b/drivers/net/i40e/i40e_flow.c
index 6a22deb..4c7856c 100644
--- a/drivers/net/i40e/i
This patch adds i40e_flow_flush function to flush all
filters for users. And flow director flush function
is involved first.
Signed-off-by: Beilei Xing
---
drivers/net/i40e/i40e_ethdev.h | 3 +++
drivers/net/i40e/i40e_fdir.c | 8 ++--
drivers/net/i40e/i40e_flow.c | 46 +
This patch adds i40e_dev_destroy_tunnel_filter function
to destroy a tunnel filter for users.
Signed-off-by: Beilei Xing
---
drivers/net/i40e/i40e_ethdev.c | 10 ++
drivers/net/i40e/i40e_ethdev.h | 5 +
drivers/net/i40e/i40e_flow.c | 41 +
3
This patch adds i40e_flow_destroy function to destroy
a flow for users.
Signed-off-by: Beilei Xing
---
drivers/net/i40e/i40e_flow.c | 29 +
1 file changed, 29 insertions(+)
diff --git a/drivers/net/i40e/i40e_flow.c b/drivers/net/i40e/i40e_flow.c
index 6a8c3a7..2a61c4
This patch adds i40e_dev_destroy_ethertype_filter function
to destroy a ethertype filter for users.
Signed-off-by: Beilei Xing
---
drivers/net/i40e/i40e_ethdev.c | 10 ++---
drivers/net/i40e/i40e_ethdev.h | 5 +
drivers/net/i40e/i40e_flow.c | 51 +++
This patch adds i40e_flow_create function to create a
rule. It will check if a flow matches ethertype filter
or flow director filter or tunnel filter, if the flow
matches some kind of filter, then set the filter to HW.
Signed-off-by: Beilei Xing
---
drivers/net/i40e/i40e_ethdev.c | 9 +++--
dri
This patch adds i40e_parse_tunnel_filter to check if
a rule is a tunnel rule according to items of the flow
pattern, and the function also gets the tunnel info.
Signed-off-by: Beilei Xing
---
drivers/net/i40e/i40e_flow.c | 390 +++
1 file changed, 390 inse
This patch adds i40e_parse_fdir_filter to check if a rule
is a flow director rule according to the flow pattern,
and the function also gets the flow director info.
Signed-off-by: Beilei Xing
---
drivers/net/i40e/i40e_ethdev.c | 56 +---
drivers/net/i40e/i40e_ethdev.h | 55
drivers/net/i40
This patch adds i40e_flow_validation function to check if
a flow is valid according to the flow pattern.
i40e_parse_ethertype_filter is added first, it also gets
the ethertype info.
i40e_flow.c is added to handle all generic filter events.
Signed-off-by: Beilei Xing
---
drivers/net/i40e/Makefile
Add support of restoring flow director filter.
Signed-off-by: Beilei Xing
---
drivers/net/i40e/i40e_ethdev.c | 1 +
drivers/net/i40e/i40e_ethdev.h | 1 +
drivers/net/i40e/i40e_fdir.c | 12
3 files changed, 14 insertions(+)
diff --git a/drivers/net/i40e/i40e_ethdev.c b/drivers/n
Currently there's no tunnel filter stored in SW.
This patch stores tunnel filter in SW with cuckoo
hash, also adds protection if a tunnel filter has
been added.
Signed-off-by: Beilei Xing
---
drivers/net/i40e/i40e_ethdev.c | 167 -
drivers/net/i40e/i40e_et
Add support of restoring tunnel filter.
Signed-off-by: Beilei Xing
---
drivers/net/i40e/i40e_ethdev.c | 21 +
1 file changed, 21 insertions(+)
diff --git a/drivers/net/i40e/i40e_ethdev.c b/drivers/net/i40e/i40e_ethdev.c
index cd7c309..7b4c426 100644
--- a/drivers/net/i40e/i4
Add support of restoring ethertype filter in case filter
dropped accidentally, as all filters need to be added and
removed by user obviously for generic filter API.
Signed-off-by: Beilei Xing
---
drivers/net/i40e/i40e_ethdev.c | 39 +++
1 file changed, 39 inse
Currently there's no ethertype filter stored in SW.
This patch stores ethertype filter with cuckoo hash
in SW, also adds protection if an ethertype filter
has been added.
Signed-off-by: Beilei Xing
---
drivers/net/i40e/Makefile | 1 +
drivers/net/i40e/i40e_ethdev.c | 164 +
All pathes depend on Adrien's Generic flow API(rte_flow).
The patches mainly finish following functions:
1) Store and restore all kinds of filters.
2) Parse all kinds of filters.
3) Add flow validate function.
4) Add flow create function.
5) Add flow destroy function.
6) Add flow flush function.
Currently there's no flow director filter stored in SW. This
patch stores flow director filters in SW with cuckoo hash,
also adds protection if a flow director filter has been added.
Signed-off-by: Beilei Xing
---
drivers/net/i40e/i40e_ethdev.c | 48 +
drivers/net/i40e/i40e_e
On Tue, Dec 27, 2016 at 01:33:14PM +0800, wang.yon...@zte.com.cn wrote:
> There are some descriptions in
> dpdk-16.11\doc\guides\sample_app_ug\vhost.rst,
> "The sample application performs simple packet switching between virtual
> machines based on Media Access Control (MAC) address or Virtual
There are some descriptions in
dpdk-16.11\doc\guides\sample_app_ug\vhost.rst,
"The sample application performs simple packet switching between virtual
machines based on Media Access Control (MAC) address or Virtual Local Area
Network (VLAN) tag." So, we want to use vhost-switch between two VM
Hello.
Ferruh, Thomas, is there a chance for this to be accepted to 17.02?
Maybe I should resend this patch-set without 'RFC' tag?
Best regards, Ilya Maximets.
On 21.11.2016 16:53, Ferruh Yigit wrote:
> On 10/19/2016 3:30 PM, Ferruh Yigit wrote:
>> On 10/19/2016 3:07 PM, Ilya Maximets wrote:
>>>
Hi, Adrien
> -Original Message-
> From: Adrien Mazarguil [mailto:adrien.mazarg...@6wind.com]
> Sent: Friday, December 23, 2016 4:13 PM
> To: Yigit, Ferruh
> Cc: Zhao1, Wei ; dev@dpdk.org; Lu, Wenzhuo
>
> Subject: Re: [dpdk-dev] [PATCH 15/18] net/ixgbe: parse flow director filter
>
> Hi
Hi Adrien,
On Mon, Dec 26, 2016 at 04:15:37PM +0100, Adrien Mazarguil wrote:
> Hi Tiwei,
>
> On Sun, Dec 25, 2016 at 10:57:54PM +0800, Tiwei Bie wrote:
> > This patch set adds the MACsec offload support for ixgbe.
> > The testpmd is also updated to support MACsec cmds.
>
> I'm not commenting on
> -Original Message-
> From: De Lara Guarch, Pablo
> Sent: Monday, December 19, 2016 5:29 PM
> To: Doherty, Declan
> Cc: dev@dpdk.org; De Lara Guarch, Pablo
> Subject: [PATCH v3 0/4] AESNI MB PMD updates
>
> The library used in AESNI MB PMD, Intel Multi Buffer Crypto for IPsec,
> has bee
> -Original Message-
> From: Kusztal, ArkadiuszX
> Sent: Friday, December 23, 2016 12:51 PM
> To: dev@dpdk.org
> Cc: Trahe, Fiona; De Lara Guarch, Pablo; Griffin, John; Jain, Deepak K;
> Kusztal, ArkadiuszX
> Subject: [PATCH v3 0/2] Add scatter-gather list capability to Intel(R)
> QuickAs
Dseg pointer is not initialised when the first segment is inlined
causing a segmentation fault in such situation.
Fixes: 2a66cf378954 ("net/mlx5: support inline send")
CC: sta...@dpdk.org
Signed-off-by: Shahaf Shuler
---
drivers/net/mlx5/mlx5_rxtx.c | 6 +-
1 file changed, 5 insertions(+),
Hi Tiwei,
On Sun, Dec 25, 2016 at 10:57:54PM +0800, Tiwei Bie wrote:
> This patch set adds the MACsec offload support for ixgbe.
> The testpmd is also updated to support MACsec cmds.
I'm not commenting on any specific patch from this series, however I'm
noticing this new trend of working around e
Hi,
We have implemented a packet processing application using Intel DPDK
2.1.0.
The system uses linux kernel 4.4.2 and has a mix of 1Gbps ( Intel i350
NIC ) and 10Gbps( Intel XL710 NIC) interfaces.
The system has 2 NUMA nodes , with each NUMA node running 5 packet
processing threads.
On Monday 26 December 2016 06:20 PM, Shreyansh Jain wrote:
When a PMD is registred, it will associate itself with a bus.
A bus is responsible for 'scan' of all the devices attached to it.
All the scanned devices are attached to bus specific device_list.
During the probe operation, 'match' of the
Three macros:
FOREACH_BUS
FOREACH_DEVICE_ON_BUS
FOREACH_DRIVER_ON_BUS
are introduced to make looping over bus (on global list), devices and
drivers (on a specific bus) prettier.
Signed-off-by: Shreyansh Jain
---
app/test/test_pci.c | 12 ++--
lib/librte_eal/common/
From: Ben Walker
Instead of passing domain, bus, devid, func, just pass
an rte_pci_addr.
Signed-off-by: Ben Walker
[Shreyansh: Checkpatch error fix]
Signed-off-by: Shreyansh Jain
---
lib/librte_eal/linuxapp/eal/eal_pci.c | 33 ++---
1 file changed, 14 insertions(+)
These callbacks now act as first layer of PCI interfaces from the Bus.
Bus probe would enter the PMDs through the rte_driver->probe/remove
callbacks, falling to rte_xxx_driver->probe/remove (Currently, all the
drivers are rte_pci_driver).
This patch also changes QAT which is the only crypto PMD ba
Register a PCI bus with Scan/match and probe callbacks. Necessary changes
in EAL layer for enabling bus interfaces. PCI devices and drivers now
reside within the Bus object.
Now that PCI bus handles the scan/probe methods, independent calls to
PCI scan and probe can be removed from the code.
PCI d
The model is:
rte_eal_init
`--> calls rte_eal_bus_probe()
This iterates over all the drivers and devices and matches them. For
matched bus specific device-driver and calls:
`-> rte_driver->probe()
for all matched device/drivers (rte_bus->match() successful)
T
rte_driver now supports probe and remove. These would be used for generic
device type (PCI, etc) probe and remove.
Signed-off-by: Shreyansh Jain
---
lib/librte_eal/common/include/rte_dev.h | 12
1 file changed, 12 insertions(+)
diff --git a/lib/librte_eal/common/include/rte_dev.h
Matching of PCI device address and driver ID table is being done at two
discreet locations duplicating the code. (rte_eal_pci_probe_one_driver
and rte_eal_pci_detach_dev).
Splitting the matching function into rte_eal_pci_match.
Signed-off-by: Shreyansh Jain
--
v2:
- Change default return in ma
Still a dummy implementation as no real bus driver exists. This adds calls
from EAL to bus specific scan, match functions.
Once driver->probe is in place, and a bus handler has been installed,
the code would become effective.
Signed-off-by: Shreyansh Jain
---
lib/librte_eal/bsdapp/eal/eal.c
PCI scan and match now work on rte_device/rte_driver rather than PCI
specific objects. These functions can now be plugged to the generic
bus callbacks for scanning and matching devices/drivers.
Signed-off-by: Shreyansh Jain
---
app/test/test_pci.c | 2 +-
lib/librte_eal/bsda
When a PMD is registred, it will associate itself with a bus.
A bus is responsible for 'scan' of all the devices attached to it.
All the scanned devices are attached to bus specific device_list.
During the probe operation, 'match' of the drivers and devices would
be done.
Also, rather than adding
This patch introduces the rte_bus abstraction for devices and drivers in
EAL framework. The model is:
- One or more buses are connected to a CPU (or core)
- One or more devices are conneted to a Bus
- Drivers are running instances which manage one or more devices
- Bus is responsible for identi
Verification of bus registration, driver registration on a bus.
Signed-off-by: Shreyansh Jain
---
app/test/Makefile | 2 +-
app/test/test.h | 2 +
app/test/test_bus.c | 424
3 files changed, 427 insertions(+), 1 deletion(-)
create m
Link to v1: [10]
Link to v2: [11]
Link to v3: [13]
Link to v4: [14]
:: Introduction ::
DPDK has been inherently a PCI inclined framework. Because of this, the
design of device tree (or list) within DPDK is also PCI inclined. A
non-PCI device doesn't have a way of being expressed without using hoo
From: Ben Walker
Instead of passing domain, bus, devid, func, just pass
an rte_pci_addr.
Signed-off-by: Ben Walker
[Shreyansh: Checkpatch error fix]
Signed-off-by: Shreyansh Jain
---
lib/librte_eal/linuxapp/eal/eal_pci.c | 33 ++---
1 file changed, 14 insertions(+)
Three macros:
FOREACH_BUS
FOREACH_DEVICE_ON_BUS
FOREACH_DRIVER_ON_BUS
are introduced to make looping over bus (on global list), devices and
drivers (on a specific bus) prettier.
Signed-off-by: Shreyansh Jain
---
app/test/test_pci.c | 12 ++--
lib/librte_eal/common/
Register a PCI bus with Scan/match and probe callbacks. Necessary changes
in EAL layer for enabling bus interfaces. PCI devices and drivers now
reside within the Bus object.
Now that PCI bus handles the scan/probe methods, independent calls to
PCI scan and probe can be removed from the code.
PCI d
These callbacks now act as first layer of PCI interfaces from the Bus.
Bus probe would enter the PMDs through the rte_driver->probe/remove
callbacks, falling to rte_xxx_driver->probe/remove (Currently, all the
drivers are rte_pci_driver).
This patch also changes QAT which is the only crypto PMD ba
Matching of PCI device address and driver ID table is being done at two
discreet locations duplicating the code. (rte_eal_pci_probe_one_driver
and rte_eal_pci_detach_dev).
Splitting the matching function into rte_eal_pci_match.
Signed-off-by: Shreyansh Jain
--
v2:
- Change default return in ma
PCI scan and match now work on rte_device/rte_driver rather than PCI
specific objects. These functions can now be plugged to the generic
bus callbacks for scanning and matching devices/drivers.
Signed-off-by: Shreyansh Jain
---
app/test/test_pci.c | 2 +-
lib/librte_eal/bsda
The model is:
rte_eal_init
`--> calls rte_eal_bus_probe()
This iterates over all the drivers and devices and matches them. For
matched bus specific device-driver and calls:
`-> rte_driver->probe()
for all matched device/drivers (rte_bus->match() successful)
T
Still a dummy implementation as no real bus driver exists. This adds calls
from EAL to bus specific scan, match functions.
Once driver->probe is in place, and a bus handler has been installed,
the code would become effective.
Signed-off-by: Shreyansh Jain
---
lib/librte_eal/bsdapp/eal/eal.c
When a PMD is registred, it will associate itself with a bus.
A bus is responsible for 'scan' of all the devices attached to it.
All the scanned devices are attached to bus specific device_list.
During the probe operation, 'match' of the drivers and devices would
be done.
Also, rather than adding
rte_driver now supports probe and remove. These would be used for generic
device type (PCI, etc) probe and remove.
Signed-off-by: Shreyansh Jain
---
lib/librte_eal/common/include/rte_dev.h | 12
1 file changed, 12 insertions(+)
diff --git a/lib/librte_eal/common/include/rte_dev.h
Verification of bus registration, driver registration on a bus.
Signed-off-by: Shreyansh Jain
---
app/test/Makefile | 2 +-
app/test/test.h | 2 +
app/test/test_bus.c | 424
3 files changed, 427 insertions(+), 1 deletion(-)
create m
This patch introduces the rte_bus abstraction for devices and drivers in
EAL framework. The model is:
- One or more buses are connected to a CPU (or core)
- One or more devices are conneted to a Bus
- Drivers are running instances which manage one or more devices
- Bus is responsible for identi
Link to v1: [10]
Link to v2: [11]
Link to v3: [13]
:: Introduction ::
DPDK has been inherently a PCI inclined framework. Because of this, the
design of device tree (or list) within DPDK is also PCI inclined. A
non-PCI device doesn't have a way of being expressed without using hooks
started from E
On Fri, Dec 23, 2016 at 12:21:10PM +, Ferruh Yigit wrote:
> On 12/21/2016 3:19 PM, Nelio Laranjeiro wrote:
> > Convert Ethernet, IPv4, IPv6, TCP, UDP layers into ibv_flow and create
> > those rules when after validation (i.e. NIC supports the rule).
> >
> > VLAN is still not supported in this
Hi, Vincent,
Since original patch set are split into 2 different patches, can
we discuss in this thread?
Attach original discussion below. Sorry for top-post.
>
> Le 22/12/2016 à 09:10, Chen, Jing D a écrit :
> > In the meanwhile, we have some test models ongoing to validate
> > combination of
Vincent,
Sorry, I missed this reply.
>
> Le 22/12/2016 à 09:10, Chen, Jing D a écrit :
> > In the meanwhile, we have some test models ongoing to validate
> > combination of Linux and DPDK drivers for VF and PF. We'll fully support
> below 4 cases going forward.
> > 1. DPDK PF + DPDK VF
> > 2. DP
On Friday 16 December 2016 03:06 AM, Jan Blunck wrote:
On Wed, Dec 14, 2016 at 10:49 AM, Shreyansh Jain wrote:
On Tuesday 13 December 2016 07:07 PM, Shreyansh Jain wrote:
These callbacks now act as first layer of PCI interfaces from the Bus.
Bus probe would enter the PMDs through the rte_driv
> -Original Message-
> From: Sexton, Rory
> Sent: Friday, December 9, 2016 10:03 PM
> To: Wu, Jingjing
> Cc: dev@dpdk.org; Marjanovic, Nemanja ;
> Mcnamara, John
> Subject: RE: [PATCH v1] net/i40e: set no drop for traffic class
>
> Hi Jingjing,
>
> Yes PRTDCB_TC2PFC is used to control
As discussed offline, this will lead to many DRIVER OK among
dev_stop()/dev_start(). I'll remove this patch.
Thanks,
Jianfeng
> -Original Message-
> From: Yuanhan Liu [mailto:yuanhan@linux.intel.com]
> Sent: Monday, December 26, 2016 4:02 PM
> To: Tan, Jianfeng
> Cc: dev@dpdk.org; Yi
On Mon, Dec 26, 2016 at 06:55:16AM +, Tan, Jianfeng wrote:
>
>
> > -Original Message-
> > From: Yuanhan Liu [mailto:yuanhan@linux.intel.com]
> > Sent: Monday, December 26, 2016 2:27 PM
> > To: Tan, Jianfeng
> > Cc: dev@dpdk.org; Yigit, Ferruh; Liang, Cunming
> > Subject: Re: [PATC
63 matches
Mail list logo
