On 13.10.2018 06:24, Jack Min wrote:
rewrite TTL by decrease or just set it directly
it's not necessary to check if the final result
is zero or not
This is slightly different from the one defined
by openflow and more generic
Signed-off-by: Xiaoyu Min
Acked-by: Yongseok Koh
---
[...]
diff
12/10/2018 13:07, Dumitrescu, Cristian:
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> > 01/10/2018 19:30, Cristian Dumitrescu:
> > > http://dpdk.org/git/next/dpdk-next-pipeline
> >
> > Please, could you fix the names in author fields and signed-off, etc?
> > Example: "Zhang, Roy Fan" sh
Hi Moty,
Thursday, October 11, 2018 4:05 PM, Mordechay Haimovsky:
> Subject: [PATCH v2 1/2] net/mlx5: refactor TC-flow infrastructure
>
> This commit refactors tc_flow as a preparation to coming commits that sends
> different type of messages and expect differ type of replies while still using
>
Hi Moty,
In addition to below, the prefix for each tc flow function should be
flow_tcf_*. Make sure to update your functions.
Thursday, October 11, 2018 4:05 PM, Mordechay Haimovsky:
> Subject: [PATCH v2 2/2] net/mlx5: support e-switch flow count action
>
> This commit adds support for config
The function mlx5_dev_to_port_id() is returning all the ports
associated to a rte_device.
It was comparing driver names while already comparing rte_device pointers.
If two devices are the same, they will have the same driver.
So the useless driver name comparison is removed.
Signed-off-by: Thomas
The logs printed by CDEV_LOG_* were prefixed with the driver name.
In order to avoid assigning the driver before the end of the probing,
the driver name is removed from the cryptodev library logs.
Signed-off-by: Thomas Monjalon
---
lib/librte_cryptodev/rte_cryptodev_pmd.c | 23 -
The helper rte_eth_dma_zone_reserve() is called by PMDs
when probing a new port.
It creates a new memzone with an unique name.
The name of this memzone was using the name of the driver
doing the probe.
In order to avoid assigning the driver before the end of the probing,
the driver name is removed
In the devargs syntax for device representors, it is possible to add
several devices at once: -w dbdf,representor=[0-3]
It will become a more frequent case when introducing wildcards
and ranges in the new devargs syntax.
If a devargs string is provided for probing, and updated with a bigger
range
The function rte_dev_is_probed() is added in order to improve semantic
and enforce proper check of the probing status of a device.
It will answer this rte_device query:
Is it already successfully probed or not?
Signed-off-by: Thomas Monjalon
Reviewed-by: Andrew Rybchenko
Tested-by: Andrew Rybch
The PCI mapping requires to know the PCI driver to use,
even before the probing is done. That's why the PCI driver is
referenced early inside the PCI device structure. See
commit 1d20a073fa5e ("bus/pci: reference driver structure before mapping")
However the rte_driver does not need to be referenc
The logs printed by COMPRESSDEV_LOG were prefixed with the driver name.
In order to avoid assigning the driver before the end of the probing,
the driver name is removed from the compressdev library logs.
Signed-off-by: Thomas Monjalon
---
lib/librte_compressdev/rte_compressdev_pmd.c | 23 ++
This is a follow-up of an idea presented at Dublin
during the "hotplug talk".
The idea is to ease probing of range of ports attached
to the same rte_device.
I becomes possible to allow probing again the same device
but with a bigger range of ports in the devargs.
Instead of adding a parameter to
+Cc Yongseok and Shahaf
14/10/2018 22:47, Thomas Monjalon:
> The function mlx5_dev_to_port_id() is returning all the ports
> associated to a rte_device.
> It was comparing driver names while already comparing rte_device pointers.
> If two devices are the same, they will have the same driver.
> So
+Cc vmbus, ifpga, i40e, mlx and szedata2 maintainers
14/10/2018 22:47, Thomas Monjalon:
> The PCI mapping requires to know the PCI driver to use,
> even before the probing is done. That's why the PCI driver is
> referenced early inside the PCI device structure. See
> commit 1d20a073fa5e ("bus/pci:
The function rte_eth_dev_detach() is freeing a port and its underlying
rte_device object. The issue is that we may have several ports
associated to the same rte_device.
The right replacement is to free the port, and free the rte_device
if no more ports.
At ethdev level, the public function for por
This is a clean-up of common ethdev data freeing.
All data freeing are moved to rte_eth_dev_release_port()
and done only in case of primary process.
It is probably fixing some memory leaks for PMDs which were
not freeing all data.
Signed-off-by: Thomas Monjalon
---
drivers/net/af_packet/rte_eth
After closing a port, it cannot be restarted.
So there is no reason to not free all associated resources.
The last step was done with rte_eth_dev_detach() which is deprecated.
Instead of blindly removing the associated rte_device, the driver should
check if no more port (ethdev, cryptodev, etc) is
If the build environment hasn't 'linux/tc_act/tc_pedit.h',
compiler will use needed structs defined in mlx5_flow_tcf.c.
However, there is a zero-size array defined in one struct and
ISO C forbids this when -Wpedantic is set by debug mode.
Simply put __extension__ keyword before the struct in ques
Hi
> > +Do not bind the ``uio_pci_generic`` module in X550 NICs.
> > +Do not bind ``igb_uio`` with legacy mode in X550 NICs.
> > +Before using ``vfio`` with legacy mode in X550 NICs, using ``modprobe
> > +vfio `` ``nointxmask=1`` to bind ``vfio``.
>
> I have couple questions here.
> If noinitxmas
Hi， Ilya Maximets
> -Original Message-
> From: Ilya Maximets [mailto:i.maxim...@samsung.com]
> Sent: Friday, October 12, 2018 6:15 PM
> To: Zhao1, Wei ; Zhang, Qi Z ;
> Laurent Hardy
> Cc: Lu, Wenzhuo ; Ananyev, Konstantin
> ; sta...@dpdk.org; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH
Hi Wei:
> -Original Message-
> From: Zhao1, Wei
> Sent: Thursday, October 11, 2018 1:10 AM
> To: Zhang, Qi Z ; mocan
> Cc: dev@dpdk.org; Lu, Wenzhuo
> Subject: RE: Re:RE: [dpdk-dev] [PATCH] net/ixgbe: put 5tuple check in front
> to jump over ntuple filter case
>
> Hi, qi
>
> > -Ori
Hi Ferruh,
Please find the answers embedded to the email.
>
> On 10/12/2018 12:35 PM, Vipin Varghese wrote:
> > With the latest release, support for vdev ethernet devices like pcap,
> > tun and tap are been added. Hence collecting statistics using
> > proc-info is possible now.
>
> This sup
When using uio_pci_generic module or using legacy interrupt mode of
igb_uio or vfio, X550 cannot get interrupts. Because the Interrupt
Status bit is not implemented, then the irq cannot be handled correctly
and cannot report the event fd to DPDK apps.
Add this hw limitation and details into ixgbe
Monday, October 15, 2018 4:45 AM, Jack Min:
> Subject: [PATCH] net/mlx5: fix compiling issue of zero-size array
>
> If the build environment hasn't 'linux/tc_act/tc_pedit.h', compiler will use
> needed structs defined in mlx5_flow_tcf.c.
>
> However, there is a zero-size array defined in one stru
Sunday, October 14, 2018 11:49 PM, Thomas Monjalon:
> 14/10/2018 22:47, Thomas Monjalon:
> > The function mlx5_dev_to_port_id() is returning all the ports
> > associated to a rte_device.
> > It was comparing driver names while already comparing rte_device
> pointers.
> > If two devices are the same
> -Original Message-
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> Sent: Monday, October 15, 2018 4:54
> To: dev@dpdk.org
> Cc: gaetan.ri...@6wind.com; ophi...@mellanox.com; Zhang, Qi Z
> ; Yigit, Ferruh ;
> re...@netcope.com; Xing, Beilei ;
> shah...@mellanox.com; ys...@mellano
On Saturday 13 October 2018 09:38 PM, Pavan Nikhilesh wrote:
> On Sat, Oct 13, 2018 at 05:51:26PM +0530, Shreyansh Jain wrote:
>> In case RTE_LIBRTE_DPAA2_USE_PHYS_IOVA is enabled, only supported
>> class is RTE_IOVA_PA.
>>
>> Fixes: f7768afac101 ("bus/fslmc: support dynamic IOVA")
>> Cc: hemant.ag
> -Original Message-
> From: Kovacevic, Marko
> Sent: Friday, October 12, 2018 4:45 PM
> To: dev@dpdk.org
> Cc: Zhang, Roy Fan ; akhil.go...@nxp.com;
> Kusztal, ArkadiuszX ; Kovacevic, Marko
>
> Subject: [PATCH v4 0/8] FIPS validation capability
>
> This sample application is made for
With this patch, dpaa bus and ethernet devices on this bus
would start using the physical-virtual library interfaces.
This patch impacts mempool/dpaa, event/dpaa and net/dpaa as
they are dependent on the bus/dpaa and thus impact linkage of
libraries.
Signed-off-by: Shreyansh Jain
---
drivers/bu
A common library, valid for dpaaX drivers, which is used to maintain
a local copy of PA->VA translations.
In case of physical addressing mode (one of the option for FSLMC, and
only option for DPAA bus), the addresses of descriptors Rx'd are
physical. These need to be converted into equivalent VA f
Prior to this patch, bus and common compiled parallel. But, post this
dependency is created.
This is especially important for the DPAA/FSLMC buses which are going
to use the common/dpaax library.
Signed-off-by: Shreyansh Jain
---
drivers/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --gi
In case RTE_LIBRTE_DPAA2_USE_PHYS_IOVA is enabled, only supported
class is RTE_IOVA_PA.
Fixes: f7768afac101 ("bus/fslmc: support dynamic IOVA")
Cc: hemant.agra...@nxp.com
Signed-off-by: Shreyansh Jain
---
drivers/bus/fslmc/fslmc_bus.c | 4
1 file changed, 4 insertions(+)
diff --git a/driv
::Background::
After the restructuring of memory in last release(s), one of the
major impact on fslmc/dpaa bus (and its devices) was the performance
drop when using physical addressing.
Previously, it was assumed that physical range was contiguous for
any given request for hugepage memory. That wa
With this patch, fslmc bus and ethernet devices on this bus
would start using the physical-virtual library interfaces.
This patch impacts mempool/dpaa2, event/dpaa2, net/dpaa2,
raw/dpaa2_cmdif and raw/dpaa2_qdma as they are dependent
on the bus/fslmc and thus impact linkage of libraries.
Signed-o
34 matches
Mail list logo
