> -Original Message-
> From: dev On Behalf Of Dekel Peled
> Sent: Sunday, September 16, 2018 9:42 PM
> To: dev@dpdk.org; Shahaf Shuler ; Yongseok Koh
>
> Cc: Ori Kam
> Subject: [dpdk-dev] [PATCH] net/mlx5: support metadata as flow rule criteria
>
> As described in series starting at
Flow engine has to support multiple driver paths. Verbs/DV for NIC flow
steering and Linux TC flower for E-Switch flow steering. In the future,
another flow driver could be added (devX).
Signed-off-by: Yongseok Koh
---
drivers/net/mlx5/mlx5.c| 1 -
drivers/net/mlx5/mlx5_flow.c
Netlink based E-Switch flow engine will be migrated to the new flow engine.
nl_flow will be renamed to flow_tcf as it goes through Linux TC flower
interface.
Signed-off-by: Yongseok Koh
---
drivers/net/mlx5/Makefile |1 -
drivers/net/mlx5/mlx5.c | 32 -
drivers/net/mlx5/mlx5.
This patchset is to migrate the existing E-Switch flow driver on to the new flow
engine. This patchset depends on Ori's new flow engine [1].
[1] http://patches.dpdk.org/project/dpdk/list/?series=1380
Yongseok Koh (3):
net/mlx5: add abstraction for multiple flow drivers
net/mlx5: remove Netlin
Flows having 'transfer' attribute have to be inserted to E-Switch on the
NIC and the control path uses Linux TC flower interface via Netlink socket.
This patch adds the flow driver on top of the new flow engine.
Signed-off-by: Yongseok Koh
---
drivers/net/mlx5/Makefile|1 +
drivers/n
> -Original Message-
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Tomasz Cel
> Sent: Wednesday, September 19, 2018 7:27 AM
> To: dev@dpdk.org
> Cc: sta...@dpdk.org; akhil.go...@nxp.com; Kovacevic, Marko
> ; Cel,
> TomaszX
> Subject: [dpdk-dev] [PATCH v2] doc/crypto: fix missi
Hello Ferruh,
On Fri, Sep 14, 2018 at 1:37 PM, Ferruh Yigit wrote:
> On 9/4/2018 11:02 AM, Shahaf Shuler wrote:
>> Tuesday, September 4, 2018 1:13 PM, Ferruh Yigit:
>>> Subject: [PATCH v2] ethdev: make default behavior CRC strip on Rx
>>>
>>> Removed DEV_RX_OFFLOAD_CRC_STRIP offload flag.
>>> Wit
On 09/15/2018 07:20 AM, Nikolay Nikolaev wrote:
Introduce vhost_message_handlers, which maps the message request
type to the message handler. Then replace the switch construct
with a map and call.
Failing vhost_user_set_features is fatal and all processing should
stop immediately and propagat
Hello Bruce, Luca, Rami and Stephen,
Could you please help to review the change?
Any comments are welcome.
Thanks a lot!
Br,
Tone
-Original Message-
From: dev On Behalf Of tone.zhang
Sent: Wednesday, September 5, 2018 1:18 PM
To: dev@dpdk.org
Cc: Gavin Hu (Arm Technology China) ;
br
This patch fixes the issue that representor port shows xstats of PF.
Fixes: 2b7302638898 ("net/mlx5: probe all port representors")
Cc: adrien.mazarg...@6wind.com
Signed-off-by: Xueming Li
---
drivers/net/mlx5/mlx5_stats.c | 13 +
1 file changed, 9 insertions(+), 4 deletions(-)
diff
> Update the QAT documentation to show that it supports CCM.
>
> Fixes: ab56c4d9ed9a ("crypto/qat: support AES-CCM")
>
> Signed-off-by: Tomasz Cel
> ---
> doc/guides/cryptodevs/features/qat.ini | 3 +++
> doc/guides/cryptodevs/qat.rst | 1 +
> 2 files changed, 4 insertions(+)
Acked-by
Currently, lib latencystats works as follow:
* For every sample period, one packet is selected by RX callback to be later
used for latency measurement. That packet is marked with a timestamp.
* In TX callback, mbufs with non-zero timestamp are used for calculation.
I see a problem
The timestamp of a mbuf should be cleared after that mbuf was used for
latency calculation, otherwise future packets which reuse the same mbuf
would inherit that previous timestamp. The latencystats library looks
for mbuf with non-zero timestamp, thus incorrectly inherited value would
result in inc
The timestamp of a mbuf should be cleared after that mbuf was used for
latency calculation, otherwise future packets which reuse the same mbuf
would inherit that previous timestamp. The latencystats library looks
for mbuf with non-zero timestamp, thus incorrectly inherited value would
result in inc
Current code uses PF links status for representor port, not the
representor
interface itself. This caused wrong representor port link status when
toggling linterface up or down.
Fixes: 2b7302638898 ("net/mlx5: probe all port representors")
Cc: adrien.mazarg...@6wind.com
Signed-off-by: Xueming Li
On Tue, Sep 18, 2018 at 10:48:30PM +0200, Thomas Monjalon wrote:
> 18/09/2018 16:58, Luca Boccassi:
> > Signed-off-by: Luca Boccassi
> > ---
> > drivers/net/avf/base/meson.build | 20
> > drivers/net/avf/meson.build | 19 +++
> > drivers/net/meson.build
17/09/2018 14:45, David Marchand:
> __rte_mbuf_raw_free and __rte_pktmbuf_prefree_seg have been deprecated for
> a long time now (early 17.05), are not part of the abi and are easily
> replaced with existing api.
>
> Signed-off-by: David Marchand
> Acked-by: Andrew Rybchenko
Applied, thanks
19/09/2018 10:31, Bruce Richardson:
> On Tue, Sep 18, 2018 at 10:48:30PM +0200, Thomas Monjalon wrote:
> > 18/09/2018 16:58, Luca Boccassi:
> > > Signed-off-by: Luca Boccassi
> > > ---
> > > drivers/net/avf/base/meson.build | 20
> > > drivers/net/avf/meson.build | 19 ++
27/08/2018 14:24, Anatoly Burakov:
> Currently, command-line switches for legacy mem mode or single-file
> segments mode are only stored in internal config. This leads to a
> situation where these flags have to always match between primary
> and secondary, which is bad for usability.
>
> Fix this
On 9/1/2018 5:32 AM, Ajit Khaparde wrote:
> From: Somnath Kotur
>
> There was no direct association between the rxq's vnic and the vnic_info[].
> Explicitly associate the two in bnxt_mq_rx_configure().
>
> Fixes: f7c3d72afff7 ("net/bnxt: fix Rx ring count limitation")
> Cc: sta...@dpdk.org
>
>
On 9/19/2018 10:05 AM, Ferruh Yigit wrote:
> On 9/1/2018 5:32 AM, Ajit Khaparde wrote:
>> From: Somnath Kotur
>>
>> There was no direct association between the rxq's vnic and the vnic_info[].
>> Explicitly associate the two in bnxt_mq_rx_configure().
>>
>> Fixes: f7c3d72afff7 ("net/bnxt: fix Rx ri
On 9/1/2018 5:32 AM, Ajit Khaparde wrote:
> From: Somnath Kotur
>
> bnxt_start_xmit() was attempting to access an uninitialized ptr - txbd1
> which would lead to segmentation fault.
> Fix to initialize ptr to NULL and check for the same before access.
>
> Fixes: f10258e39ec2 ("net/bnxt: fix HW T
On 9/1/2018 5:32 AM, Ajit Khaparde wrote:
> Patchset against dpdk-next-net.
> Please apply.
>
> Ajit Khaparde (5):
> net/bnxt: fix MTU setting
> net/bnxt: update HWRM version
> net/bnxt: add support for extended port counters
> net/bnxt: add support to enable new mailbox channel
> net/bn
12/09/2018 15:29, Ferruh Yigit:
> On 9/11/2018 4:00 PM, Gaetan Rivet wrote:
> > The strncpy function has long been deemed unsafe for use,
> > in favor of strlcpy or snprintf.
> >
> > While snprintf is standard and strlcpy is still largely available,
> > they both have issues regarding error checki
On Wed, Sep 19, 2018 at 10:42:50AM +0200, Thomas Monjalon wrote:
> 19/09/2018 10:31, Bruce Richardson:
> > On Tue, Sep 18, 2018 at 10:48:30PM +0200, Thomas Monjalon wrote:
> > > 18/09/2018 16:58, Luca Boccassi:
> > > > Signed-off-by: Luca Boccassi
> > > > ---
> > > > drivers/net/avf/base/meson.bu
This set adds a number of build improvements for AVF driver. It adds
support for building with meson, and adds in the $(WERROR) flags for
the make build. To fix both these cases, a number of fixes for
compiler warnings are also made.
V4: Including meson build patch into set. Added in missing revie
From: Luca Boccassi
Signed-off-by: Luca Boccassi
Reviewed-by: Bruce Richardson
---
drivers/net/avf/base/meson.build | 20
drivers/net/avf/meson.build | 18 ++
drivers/net/meson.build | 1 +
3 files changed, 39 insertions(+)
create mode 10064
Compiling with all warnings turned on causes errors about unused variables
and an unused label. Remove these to allow building without having to
disable those warnings.
Fixes: 69dd4c3d0898 ("net/avf: enable queue and device")
Fixes: 3fd7a3719c66 ("net/avf: enable ops for MTU setting")
Fixes: d6bde
The AVF driver was missing $(WERROR_FLAGS) in it's cflags, which means
that a number of compilation errors were getting missed. This patch adds
in the flag and fixes most of the errors, just disabling the
strict-aliasing ones.
Fixes: 22b123a36d07 ("net/avf: initialize PMD")
Fixes: 69dd4c3d0898 ("n
On Wed, Sep 19, 2018 at 10:45:31AM +0100, Bruce Richardson wrote:
> On Wed, Sep 19, 2018 at 10:42:50AM +0200, Thomas Monjalon wrote:
> > 19/09/2018 10:31, Bruce Richardson:
> > > On Tue, Sep 18, 2018 at 10:48:30PM +0200, Thomas Monjalon wrote:
> > > > 18/09/2018 16:58, Luca Boccassi:
> > > > > Sign
On Wed, 2018-09-19 at 11:08 +0100, Bruce Richardson wrote:
> On Wed, Sep 19, 2018 at 10:45:31AM +0100, Bruce Richardson wrote:
> > On Wed, Sep 19, 2018 at 10:42:50AM +0200, Thomas Monjalon wrote:
> > > 19/09/2018 10:31, Bruce Richardson:
> > > > On Tue, Sep 18, 2018 at 10:48:30PM +0200, Thomas Monj
Any suggestion about this issue?
Il 12/09/2018 09:38, Matteo Lanzuisi ha scritto:
Hi all,
maybe a bug or something I'm doing wrong: I'm using the example
flow_filtering on a RedHat 7.5, kernel 3.10.0-862.6.3.el7.x86_64 with
i40e and X710.
DPDK is 18.08 and configuration is x86_64-native-lin
On Wed, Sep 19, 2018 at 08:24:01AM +0530, Rao, Nikhil wrote:
> On 9/5/2018 7:15 PM, Pavan Nikhilesh wrote:
> > Signed-off-by: Pavan Nikhilesh
> > ---
> > This patch depends on the following series:
> > http://patches.dpdk.org/project/dpdk/list/?series=1121
> >
> > examples/eventdev_pipeline/
On Wed, 2018-09-05 at 13:17 +0800, tone.zhang wrote:
> If the devices used for DPDK are bound to the "uio_pci_generic"
> kernel
> module, the IOMMU should be disabled in order not to break the IO
> transmission because of the virtual / physical address mapping.
>
> The patch clarifies the IOMMU co
On 18/09/2018 10:52, Thomas Monjalon wrote:
23/08/2018 14:08, Ciara Power:
This patch adds the patch for the collectd plugin developed for use
with the DPDK Telemetry library. The patch is included here to allow
users to apply the patch to collectd when using DPDK Telemetry.
Further details on a
On Wed, Sep 19, 2018 at 07:44:36AM +, Tone Zhang (Arm Technology China)
wrote:
> Hello Bruce, Luca, Rami and Stephen,
>
> Could you please help to review the change?
>
> Any comments are welcome.
>
> Thanks a lot!
>
> Br,
> Tone
>
> -Original Message-
> From: dev On Behalf Of to
-Original Message-
> Date: Tue, 18 Sep 2018 14:45:04 +0200
> From: Mattias Rönnblom
> To: Jerin Jacob
> CC: Bruce Richardson , dev@dpdk.org, Mattias
> Rönnblom
> Subject: [PATCH v4 00/10] A Distributed Software Event Device
> X-Mailer: git-send-email 2.17.1
>
>
> v4:
> * Reworded DSW
On Wed, 2018-09-19 at 12:33 +0100, Bruce Richardson wrote:
> On Wed, Sep 19, 2018 at 07:44:36AM +, Tone Zhang (Arm Technology
> China) wrote:
> > Hello Bruce, Luca, Rami and Stephen,
> >
> > Could you please help to review the change?
> >
> > Any comments are welcome.
> >
> > Thanks a lot!
On Thursday 06 September 2018 11:24 AM, Gagandeep Singh wrote:
This patch introduces the enetc PMD with basic
initialisation functions includes probe, teardown,
hardware intialisation
Signed-off-by: Gagandeep Singh
---
MAINTAINERS | 1 +
config/common_base
On Thursday 13 September 2018 03:12 PM, Gagandeep Singh wrote:
Add RX and TX queue setup, datapath functions
and enable the packet parsing
Signed-off-by: Gagandeep Singh
---
MAINTAINERS | 1 +
drivers/net/enetc/Makefile | 3 +-
drivers/net/enetc/enetc_ethdev.c
Register and unregister the virtio interrupt handler when the device is
started and stopped. This allows a virtio device to be hotplugged or
unplugged.
Fixes: c1f86306a026 ("virtio: add new driver")
Cc: sta...@dpdk.org
Signed-off-by: Brian Russell
Signed-off-by: Luca Boccassi
---
drivers/net/v
Ok, I've added it back with a debug log in v2.
On Tue, 2018-09-18 at 18:48 +, Louis Luo wrote:
> Hi Luca,
>
> I'm fine with the queue free part, but just have concern about
> removing the check inside uninit function. If the application does
> follow the rules and keeping the check in uninit
The vmxnet3 driver can't call back into dev_close(), and possibly
dev_stop(), in dev_uninit(). When dev_uninit() is called, anything
that those routines would want to clean up has already been released.
Further, for complete cleanup, it is necessary to release any of the
queue resources during dev
If a device is unplugged while an interrupt is pending, the
read call to the uio device to remove it from the poll wait list
can fail resulting in it being continually polled forever. This
change checks for the read failing and if so, unregisters the device
as an interrupt source and causes the wai
> Anatoly Burakov (9):
> fbarray: fix detach in noshconf mode
> eal: don't allow legacy mode with in-memory mode
> mem: raise maximum fd limit unconditionally
> memalloc: rename lock list to fd list
> memalloc: track page fd's in non-single file mode
> memalloc: add EAL-internal API to
From: Phil Yang
Keep only single config option RTE_USE_C11_MEM_MODEL for C11 memory
model, so all modules can leverage C11 atomic extension by enable this
option.
Fixes: 39368eb ("ring: introduce C11 memory model barrier option")
Signed-off-by: Phil Yang
Reviewed-by: Honnappa Nagarahalli
Revie
From: Phil Yang
With existing code in kni_fifo_put, rx_q values are not being updated
before updating fifo_write. While reading rx_q in kni_net_rx_normal,
This is causing the sync issue on other core. The same situation happens
in kni_fifo_get as well.
So syncing the values by adding C11 atomic
From: Phil Yang
Adding memory barrier to make sure the values being synced
before updating fifo_write in kni_fifo_put and fifo_read in
kni_fifo_get.
Fixes: 3fc5ca2 ("kni: initial import")
Signed-off-by: Phil Yang
Reviewed-by: Honnappa Nagarahalli
Reviewed-by: Gavin Hu
---
kernel/linux/kni/kn
> > By default, testpmd will create membuf pool for all NUMA nodes and ignore
> > EAL
> > configuration.
> >
> > Count the number of available NUMA according to EAL core mask or core list
> > configuration. Optimized by only creating membuf pool for those nodes.
> >
> > Fixes: c9cafcc ("app/test
With existing code in kni_fifo_put, rx_q values are not being updated
before updating fifo_write. While reading rx_q in kni_net_rx_normal,
This is causing the sync issue on other core. The same situation happens
in kni_fifo_get as well.
So syncing the values by adding C11 atomic memory barriers to
Keep only single config option RTE_USE_C11_MEM_MODEL for C11 memory
model, so all modules can leverage C11 atomic extension by enable this
option.
Fixes: 39368eb ("ring: introduce C11 memory model barrier option")
Signed-off-by: Phil Yang
Reviewed-by: Honnappa Nagarahalli
Reviewed-by: Gavin Hu
Adding memory barrier to make sure the values being synced
before updating fifo_write in kni_fifo_put and fifo_read in
kni_fifo_get.
Fixes: 3fc5ca2 ("kni: initial import")
Signed-off-by: Phil Yang
Reviewed-by: Honnappa Nagarahalli
Reviewed-by: Gavin Hu
---
kernel/linux/kni/kni_fifo.h
From: Bruce Richardson
Signed-off-by: Bruce Richardson
Signed-off-by: Luca Boccassi
---
v2: send on behalf of Bruce on request.
- tell sphinx to create .doctrees working files in the
parent of the target directory so that they don't get
installed
- change the output director
On 19-Sep-18 2:04 PM, Thomas Monjalon wrote:
Anatoly Burakov (9):
fbarray: fix detach in noshconf mode
eal: don't allow legacy mode with in-memory mode
mem: raise maximum fd limit unconditionally
memalloc: rename lock list to fd list
memalloc: track page fd's in non-single file mod
17/09/2018 10:24, Bruce Richardson:
> On Mon, Sep 17, 2018 at 03:39:32PM +0800, Qi Zhang wrote:
> > RTE_LIBRTE_I40E_ITR_INTERVAL is not used. So it should also be removed
> > in config/rte_config.h for meson+ninjia build.
> >
> > Fixes: 864a800d706d ("net/i40e: remove VF interrupt handler")
> > Cc
Previously, to calculate length of memory area covered by a memseg
list, we would've needed to multiply page size by length of fbarray
backing that memseg list. This is not obvious and unnecessarily
low level, so store length in the memseg list itself.
Signed-off-by: Anatoly Burakov
---
drivers/
This is a proposal to enable using externally allocated memory
in DPDK.
In a nutshell, here is what is being done here:
- Index internal malloc heaps by NUMA node index, rather than NUMA
node itself (external heaps will have ID's in order of creation)
- Add identifier string to malloc heap, to
We will be assigning "invalid" socket ID's to external heap, and
malloc will now be able to verify if a supplied socket ID is in
fact a valid one, rendering parameter checks for sockets
obsolete.
Signed-off-by: Anatoly Burakov
---
lib/librte_flow_classify/rte_flow_classify.c | 3 +--
1 file chan
Switch over all parts of EAL to use heap ID instead of NUMA node
ID to identify heaps. Heap ID for DPDK-internal heaps is NUMA
node's index within the detected NUMA node list. Heap ID for
external heaps will be order of their creation.
Signed-off-by: Anatoly Burakov
---
config/common_base
We will be assigning "invalid" socket ID's to external heap, and
malloc will now be able to verify if a supplied socket ID is in
fact a valid one, rendering parameter checks for sockets
obsolete.
This changes the semantics of what we understand by "socket ID",
so document the change in the release
Add an API to remove memory from specified heaps. This will first
check if all elements within the region are free, and that the
region is the original region that was added to the heap (by
comparing its length to length of memory addressed by the
underlying memseg list).
Signed-off-by: Anatoly Bu
Add an API to destroy specified heap.
Signed-off-by: Anatoly Burakov
---
lib/librte_eal/common/include/rte_malloc.h | 23 +
lib/librte_eal/common/malloc_heap.c| 22
lib/librte_eal/common/malloc_heap.h| 3 ++
lib/librte_eal/common/rte_malloc.c | 58 ++
When we allocate and use DPDK memory, we need to be able to
differentiate between DPDK hugepage segments and segments that
were made part of DPDK but are externally allocated. Add such
a property to memseg lists.
This breaks the ABI, so bump the EAL library ABI version and
document the change in r
When we will be creating external heaps, they will have their own
"fake" socket ID, so add a function that will map the heap name
to its socket ID.
Signed-off-by: Anatoly Burakov
---
lib/librte_eal/common/include/rte_malloc.h | 14
lib/librte_eal/common/rte_malloc.c | 37 +++
Document the addition of external memory support to DPDK.
Signed-off-by: Anatoly Burakov
---
doc/guides/rel_notes/release_18_11.rst | 5 +
1 file changed, 5 insertions(+)
diff --git a/doc/guides/rel_notes/release_18_11.rst
b/doc/guides/rel_notes/release_18_11.rst
index c04685d17..cc5b582f8
We will be assigning "invalid" socket ID's to external heap, and
malloc will now be able to verify if a supplied socket ID is in
fact a valid one, rendering parameter checks for sockets
obsolete.
Signed-off-by: Anatoly Burakov
---
lib/librte_sched/rte_sched.c | 2 +-
1 file changed, 1 insertion(
Add an API to add externally allocated memory to malloc heap. The
memory will be stored in memseg lists like regular DPDK memory.
Multiple segments are allowed within a heap. If IOVA table is
not provided, IOVA addresses are filled in with RTE_BAD_IOVA.
Signed-off-by: Anatoly Burakov
---
lib/lib
Add API to allow creating new malloc heaps. They will be created
with socket ID's going above RTE_MAX_NUMA_NODES, to avoid clashing
with internal heaps.
Signed-off-by: Anatoly Burakov
---
lib/librte_eal/common/include/rte_malloc.h | 19
lib/librte_eal/common/malloc_heap.c| 30 ++
Introduce an example application demonstrating the use of
external memory support. This is a simple application based on
skeleton app, but instead of using internal DPDK memory, it is
using externally allocated memory.
The RX/TX and init path is a carbon-copy of skeleton app, with
no modifications
In order to use external memory in multiple processes, we need to
attach to primary process's memseg lists, so add a new API to do
that. It is the responsibility of the user to ensure that memory
is accessible and that it has been previously added to the malloc
heap by another process.
Signed-off-
Add a short chapter on usage of external memory in DPDK to the
Programmer's Guide.
Signed-off-by: Anatoly Burakov
---
.../prog_guide/env_abstraction_layer.rst | 38 +++
1 file changed, 38 insertions(+)
diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst
b/doc/guid
We will be assigning "invalid" socket ID's to external heap, and
malloc will now be able to verify if a supplied socket ID is in
fact a valid one, rendering parameter checks for sockets
obsolete.
Signed-off-by: Anatoly Burakov
---
lib/librte_pipeline/rte_pipeline.c | 3 +--
1 file changed, 1 ins
Add simple unit tests to test external memory support.
The tests are pretty basic and mostly consist of checking
if invalid API calls are handled correctly, plus a simple
allocation/deallocation test for malloc and memzone.
Signed-off-by: Anatoly Burakov
---
test/test/Makefile| 1 +
We will need to refer to external heaps in some way. While we use
heap ID's internally, for external API use it has to be something
more user-friendly. So, we will be using a string to uniquely
identify a heap.
Signed-off-by: Anatoly Burakov
---
lib/librte_eal/common/include/rte_malloc_heap.h |
Add API to detach from existing chunk of external memory in a
process.
Signed-off-by: Anatoly Burakov
---
lib/librte_eal/common/include/rte_malloc.h | 27 ++
lib/librte_eal/common/rte_malloc.c | 27 ++
lib/librte_eal/rte_eal_version.map |
Add a guide for external memory sample application. The application
is identical to Basic Forwarding example in everything except parts
of initialization code, so the bits that are identical will not be
described.
It is also not necessary to describe how external memory is being
allocated due to t
Added missing JUMP flow action in flow_action array.
Without this the flow rule cannot be created for JUMP action.
Fixes: 938a184a18 ("app/testpmd: implement basic support for flow API")
Signed-off-by: Reshma Pattan
---
app/test-pmd/config.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/a
19/09/2018 15:55, Burakov, Anatoly:
> On 19-Sep-18 2:04 PM, Thomas Monjalon wrote:
> >> Anatoly Burakov (9):
> >>fbarray: fix detach in noshconf mode
> >>eal: don't allow legacy mode with in-memory mode
> >>mem: raise maximum fd limit unconditionally
> >>memalloc: rename lock list t
> -Original Message-
> From: Li, Xiaoyun
> Sent: Monday, September 17, 2018 5:28 PM
> To: Zhang, Qi Z ; Lu, Wenzhuo
> ; Yigit, Ferruh
> Cc: dev@dpdk.org; Li, Xiaoyun
> Subject: [PATCH v2 0/7] update ixgbe base code
>
> Update the ixgbe base code to version cid-ixgbe.2018.08.28.tar.gz.
> -Original Message-
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ye Xiaolong
> Sent: Friday, September 14, 2018 4:40 AM
> To: Wang, Xiao W
> Cc: Bie, Tiwei ; dev@dpdk.org; Wang, Zhihong
>
> Subject: Re: [dpdk-dev] [PATCH] net/ifc: add live migration support
>
> Reviewed-and
Current Intel tx prepare function does not properly handle the
case where only IP checksum is requested, without requesting
any L4 checksum or TSO: IP checksum is not properly reset to 0
and output packet may contain invalid IP checksum.
Fixes: 4fb7e803eb1a ("ethdev: add Tx preparation")
Cc: sta..
Hi,
Sorry about the delay on this, overall it looks ok;
I have an issue however, see inline.
On Mon, Sep 03, 2018 at 07:55:22AM +0100, Andrew Rybchenko wrote:
> From: Evgeny Im
>
> Signed-off-by: Evgeny Im
> Signed-off-by: Andrew Rybchenko
> ---
> doc/guides/nics/features/failsafe.ini | 1
Hi Xiaolong,
> -Original Message-
> From: Ye, Xiaolong
> Sent: Friday, September 14, 2018 2:07 AM
> To: dev@dpdk.org; Maxime Coquelin ; Bie,
> Tiwei ; Wang, Zhihong
> Cc: Wang, Xiao W ; Rami Rosen
> ; Wang, Haiyue ; Ye,
> Xiaolong
> Subject: [PATCH v2 2/2] examples/vdpa: introduce a new
Hi,
> -Original Message-
> From: Ye, Xiaolong
> Sent: Friday, September 14, 2018 2:07 AM
> To: dev@dpdk.org; Maxime Coquelin ; Bie,
> Tiwei ; Wang, Zhihong
> Cc: Wang, Xiao W ; Rami Rosen
> ; Wang, Haiyue ; Ye,
> Xiaolong
> Subject: [PATCH v2 1/2] vhost: introduce API to get vDPA device
This patch series introduces new PMD for Marvell NETA adapters (MVNETA).
See the documentation for more info.
It is split for easier reviewing.
v4:
* rebased on top of next-net (DEV_RX_OFFLOAD_CRC_STRIP removed)
* Rx/Tx functionality moved to new mvneta_rxtx.c file
* removed eth_mvneta alia
From: Zyta Szpak
Add neta pmd driver skeleton providing base for the further
development.
Signed-off-by: Natalie Samsonov
Signed-off-by: Yelena Krivosheev
Signed-off-by: Dmitri Epshtein
Signed-off-by: Zyta Szpak
Signed-off-by: Andrzej Ostruszka
---
MAINTAINERS
From: Zyta Szpak
Add part of PMD for actual reception/transmission.
Signed-off-by: Yelena Krivosheev
Signed-off-by: Dmitri Epshtein
Signed-off-by: Zyta Szpak
---
doc/guides/nics/features/mvneta.ini | 3 +
doc/guides/nics/mvneta.rst | 4 +
drivers/net/mvneta/Makefile |
From: Zyta Szpak
Add callback for setting of MTU.
Signed-off-by: Natalie Samsonov
Signed-off-by: Zyta Szpak
---
doc/guides/nics/features/mvneta.ini | 1 +
doc/guides/nics/mvneta.rst | 1 +
drivers/net/mvneta/mvneta_ethdev.c | 78 +
3 files chang
From: Zyta Szpak
Add callback for updating information about link status/info.
Signed-off-by: Natalie Samsonov
Signed-off-by: Zyta Szpak
---
doc/guides/nics/features/mvneta.ini | 1 +
doc/guides/nics/mvneta.rst | 1 +
drivers/net/mvneta/mvneta_ethdev.c | 71 +++
From: Zyta Szpak
Add callbacks for enabling/disabling of promiscuous mode.
Signed-off-by: Yelena Krivosheev
Signed-off-by: Zyta Szpak
---
doc/guides/nics/features/mvneta.ini | 1 +
doc/guides/nics/mvneta.rst | 1 +
drivers/net/mvneta/mvneta_ethdev.c | 54 ++
From: Zyta Szpak
Add callbacks for adding/removing MAC addresses.
Signed-off-by: Yelena Krivosheev
Signed-off-by: Natalie Samsonov
Signed-off-by: Zyta Szpak
---
doc/guides/nics/features/mvneta.ini | 1 +
doc/guides/nics/mvneta.rst | 1 +
drivers/net/mvneta/mvneta_ethdev.c | 69 ++
From: Natalie Samsonov
Add support for resetting of driver statistics.
Signed-off-by: Natalie Samsonov
---
drivers/net/mvneta/mvneta_ethdev.c | 40 +++---
drivers/net/mvneta/mvneta_ethdev.h | 1 +
2 files changed, 34 insertions(+), 7 deletions(-)
diff --git a/
From: Zyta Szpak
Add support for getting of basic statistics for the driver.
Signed-off-by: Yelena Krivosheev
Signed-off-by: Natalie Samsonov
Signed-off-by: Zyta Szpak
---
doc/guides/nics/features/mvneta.ini | 1 +
doc/guides/nics/mvneta.rst | 1 +
drivers/net/mvneta/mvneta_ethdev
Hi,
for the series,
Acked-by: Gaetan Rivet
On Fri, Aug 31, 2018 at 05:09:36PM +0100, Andrew Rybchenko wrote:
> The patch series should be applied on top of [1] and [2].
>
> [1] https://patches.dpdk.org/project/dpdk/list/?series=1082
> [2] https://patches.dpdk.org/patch/43946/
>
> Ian Dolzhansk
In former API, ETH_TXQ_FLAGS_NOMULTSEGS was merely a hint indicating
that application will never send multisegmented packets, allowing
pmd to choose different tx methods accordingly.
In new API, DEV_TX_OFFLOAD_MULTI_SEGS became an offload capability
that is advertised by pmds, some of them do not a
In former API, ETH_TXQ_FLAGS_NOMULTSEGS was merely a hint indicating
that application will never send multisegmented packets, allowing
pmd to choose different tx methods accordingly.
In new API, DEV_TX_OFFLOAD_MULTI_SEGS became an offload capability
that is advertised by pmds, some of them do not a
In former API, ETH_TXQ_FLAGS_NOMULTSEGS was merely a hint indicating
that application will never send multisegmented packets, allowing
pmd to choose different tx methods accordingly.
In new API, DEV_TX_OFFLOAD_MULTI_SEGS became an offload capability
that is advertised by pmds, some of them do not a
In former API, ETH_TXQ_FLAGS_NOMULTSEGS was merely a hint indicating
that application will never send multisegmented packets, allowing
pmd to choose different tx methods accordingly.
In new API, DEV_TX_OFFLOAD_MULTI_SEGS became an offload capability
that is advertised by pmds, some of them do not a
In former API, ETH_TXQ_FLAGS_NOMULTSEGS was merely a hint indicating
that application will never send multisegmented packets, allowing
pmd to choose different tx methods accordingly.
In new API, DEV_TX_OFFLOAD_MULTI_SEGS became an offload capability
that is advertised by pmds, some of them do not a
On 14.09.2018 18:20, Ferruh Yigit wrote:
> On 8/31/2018 1:59 PM, Andrzej Ostruszka wrote:
>> This patch series introduces new PMD for Marvell NETA adapters (MVNETA).
>> See the documentation for more info.
[...]
> Hi Andrzej,
>
> Patchset is mostly looks good to me, there is no major issue but I h
1 - 100 of 172 matches
Mail list logo
