Thursday, October 18, 2018 9:29 PM, Mordechay Haimovsky:
> Subject: [PATCH v5 0/4] support e-switch flow count action
>
> The following series of patches adds support for reading the
> mlx5 e-switch flow counters.
>
> Moti Haimovsky (4):
> net/mlx5: refactor TC-flow infrastructure
> net/mlx5:
Friday, October 19, 2018 6:21 PM, Slava Ovsiienko:
> Subject: [PATCH v3 1/6] net/mlx5: flow counters object create function
> bugfix
How about: "net/mlx5: fix flow counter creation" ?
>
> The first part of patchset provides the separate commit for bugfix.
No need for this intro (exists on all
Friday, October 19, 2018 6:21 PM, Slava Ovsiienko:
> Subject: [PATCH v3 2/6] net/mlx5: flow counters new configuration flags
How about "net/mlx5: rename flow counter configuration macro" ?
>
> In this part of patchset some modifications in compile configuration flags are
> done.
Ditto.
The H
Friday, October 19, 2018 6:21 PM, Slava Ovsiienko:
> Subject: [PATCH v3 3/6] net/mlx5: flow counters simplifying runtime support
> check
How about "net/mlx5: simplify flow counters support check
>
> This part of patchset removes the redundant check of counters support in
> runtime. The flag flow
Friday, October 19, 2018 6:21 PM, Slava Ovsiienko:
> Subject: [PATCH v3 4/6] net/mlx5: flow counters mlx5 glue library update
>
How about: "net/mlx5: add new flow counter verbs API to glue library
> This part of patchset updates the mlx5 glue library, new counter support
> function pointers are
Friday, October 19, 2018 6:21 PM, Slava Ovsiienko:
> Subject: [PATCH v3 5/6] net/mlx5: flow counters query function move and
> rename
How about: "net/mlx5: relocate flow counter query function"
This patch should come before the glue library update
>
> The flow_verbs_query_count() is moved into
Friday, October 19, 2018 6:21 PM, Slava Ovsiienko:
> Subject: [PATCH v3 6/6] net/mlx5: flow counters Verbs interface functions
> update
How about: "net/mlx5: support new flow counter API"
>
> This part of patchset updates the functions performing the Verbs library calls
> in order to support di
Hi Slava,
Friday, October 19, 2018 6:21 PM, Slava Ovsiienko:
> Subject: [PATCH v3 0/6] net/mlx5: flow counters support for Linux-rdma v19
>
> Mellanox mlx5 PMD supports Flow counters via Verbs library.
> The current implementation is based on the Mellanox proprietary Verbs
> library included in
Thanks, PSB.
> -Original Message-
> From: Yongseok Koh
> Sent: Thursday, October 18, 2018 11:01 AM
> To: Dekel Peled
> Cc: Shahaf Shuler ; dev@dpdk.org; Ori Kam
>
> Subject: Re: [PATCH v4] net/mlx5: support metadata as flow rule criteria
>
> On Wed, Oct 17, 2018 at 02:53:37PM +0300, Dek
Thanks, PSB.
> -Original Message-
> From: Ori Kam
> Sent: Thursday, October 18, 2018 3:26 PM
> To: Dekel Peled ; wenzhuo...@intel.com;
> jingjing...@intel.com; bernard.iremon...@intel.com;
> olivier.m...@6wind.com; Adrien Mazarguil ;
> Thomas Monjalon ; ferruh.yi...@intel.com;
> arybche...
As described in series starting at [1], it adds option to set
metadata value as match pattern when creating a new flow rule.
This patch adds metadata support in mlx5 driver, in two parts:
- Add the validation and setting of metadata value in matcher,
when creating a new flow rule.
- Add the pass
This series implements the match-metadata feature described in [1].
[1] "[RFC v2] ethdev: support metadata as flow rule criteria"
http://mails.dpdk.org/archives/dev/2018-August/110194.html
---
v6:
Apply code review comments:
* Squash testpmd patches into single patch.
* Updat
As described in [1], a new rte_flow item is added to support metadata
to use as flow rule match pattern.
The metadata is an opaque item, fully controlled by the application.
The use of metadata is relevant for egress rules only.
It can be set in the flow rule using the RTE_FLOW_ITEM_META.
An addi
As described in [1], this series adds option to set metadata value
as match pattern when creating a new flow rule.
This patch introduces additional options in testpmd commands:
- New item type "meta" "data"
- New per-port offload flag "match_metadata".
It also adds commands to configure the tx_me
Hi Jerin,
>
> Hi Konstantin,
>
> Overall it looks good, but some comments on event mode integration in
> performance effective way.
>
> >
> > Introduce Security Association (SA-level) data-path API
> > Operates at SA level, provides functions to:
> > - initialize/teardown SA object
> >
Hi Fiona,
I do agree that your solution seems to be a neat way for organizing
capabilities. But Akhil & Thomas were against that idea and we had to come up
with one array with all capabilities. This would not scale well when we start
supporting devices with varying capabilities.
If your plan i
Dear Thomas and all,
About a month ago, I posted the topic related with
how to replace rte_eth_dev_attach.
Following your advice,
my code would be as below:
(Old code using deprecated API is commented out)
rte_eth_dev_get_port_by_name is used to retrieve dpdk port
after rte_eal_hotplug_add.
Not
Device bus should be initialized after bus scan.
While it does not happened when scan vdev from secondary process,
that cause segment fault at rte_dev_probe when call dev->bus->xxx.
Fixes: cdb068f031c6 ("bus/vdev: scan by multi-process channel")
Cc: sta...@dpdk.org
Signed-off-by: Qi Zhang
---
d
After we insert a devargs into devargs_list, following bus->scan may
destroy it due to another rte_devargs_insert. Its better not to use
a devargs pointer after it has been inserted.
Fixes: 911462eb4a5f ("eal: simplify parameters of hotplug functions")
Signed-off-by: Qi Zhang
---
lib/librte_eal
dev->devargs is not initialized for PCI device, so use dev->bus to
replace dev->devargs->bus to avoid segment fault when hotplug remove
a PCI device.
Fixes: 244d5130719c ("eal: enable hotplug on multi-process")
Signed-off-by: Qi Zhang
---
lib/librte_eal/common/eal_common_dev.c | 2 +-
1 file ch
On Friday 19 October 2018 01:09 PM, Ferruh Yigit wrote:
> On 10/18/2018 6:04 PM, Thomas Monjalon wrote:
>> 18/10/2018 18:22, Ferruh Yigit:
>>> On 10/18/2018 5:08 PM, Thomas Monjalon wrote:
Not sure we want to show the internal functions to users.
It may be useful only for PMD developers.
Hi All,
I am new to dpdk, and trying it to integrate DPDK with one of my server
having intel nic's and 24 core cpu.
I am trying to run testpmd app and it gets crashed with below logs
++
# ./testpmd-cc-on-local -c 0xF -n 1 -w 01:00.0 -- -i
EAL: Detected 24 lcor
22/10/2018 05:49, Joseph, Anoob:
> Hi Fiona,
>
> I do agree that your solution seems to be a neat way for organizing
> capabilities. But Akhil & Thomas were against that idea and we had to come up
> with one array with all capabilities. This would not scale well when we start
> supporting devic
Hi,
I am actively working on it.
Look how rte_eth_dev_attach is replaced in testpmd:
https://patches.dpdk.org/patch/47019/
It is using a new ethdev iterator RTE_ETH_FOREACH_MATCHING_DEV.
22/10/2018 06:34, Hideyuki Yamashita:
> Dear Thomas and all,
>
> About a month ago, I posted the top
24 matches
Mail list logo
