Thanks for your quick answer,
I have read so many documents and web pages on this issue that probably I
confounded the utility of the headroom. It is good to know that this 128
bytes space is available to my disposal. The fact of being lost once the
NIC transmits the frame it is not a problem at a
23/02/2018 07:25, Hemant Agrawal:
> Hi Thomas,
> On 2/23/2018 4:23 AM, Thomas Monjalon wrote:
> > The bus and mempool dependencies should be declared after the PMD
> > libraries needing them.
> >
> > Moreover there is no need to disable the PMDs at the Makefile level,
> > in case the dependencies
Hi Victor,
>
> Thanks for your quick answer,
>
> I have read so many documents and web pages on this issue that probably I
> confounded the utility of the headroom. It is good to know that this 128
> bytes space is available to my disposal. The fact of being lost once the
> NIC transmits the fra
The dynamic link is broken for ARM platform because the dependencies
of the DPAA PMD are not declared.
Fixes: 83c82e15e1c0 ("app/testpmd: support loopback config for DPAA")
Cc: sta...@dpdk.org
Reported-by: Marco Varlese
Signed-off-by: Thomas Monjalon
Signed-off-by: Hemant Agrawal
---
app/test
This patch fixes the build dependency of various
dpaaX components, when the dpaa or fslmc bus is disabled,
or VFIO is disabled.
Fixes: 1ee9569576f6 ("config: enable dpaaX drivers for generic ARMv8")
Cc: sta...@dpdk.org
Reported-by: Yongseok Koh
Suggested-by: Thomas Monjalon
Signed-off-by: Hema
On 2/23/2018 2:55 PM, Thomas Monjalon wrote:
23/02/2018 07:25, Hemant Agrawal:
Hi Thomas,
On 2/23/2018 4:23 AM, Thomas Monjalon wrote:
The bus and mempool dependencies should be declared after the PMD
libraries needing them.
Moreover there is no need to disable the PMDs at the Makefile level,
Hi all,
Victor, I suggest taking a closer look at section 7.1. here:
http://dpdk.org/doc/guides/prog_guide/mbuf_lib.html
The approach chosen by DPDK is to store everything, metadata and packet data,
in contiguous memory. That way, network packets will always have 1 to 1
relationship with DPDK m
From: Shweta Choudaha
--
2.11.0
From: Shweta Choudaha
Add ixgbe API to enable SBP bit in FCTRL register
to allow receiving packets that may otherwise be
considered length errors by ixgbe and dropped
Signed-off-by: Shweta Choudaha
Reviewed-by: Chas Williams
Reviewed-by: Luca Boccassi
---
drivers/net/ixgbe/rte_pmd_ixgbe.c
Hi Folks,
On 2/20/2018 7:29 PM, Jerin Jacob wrote:
-Original Message-
Date: Mon, 19 Feb 2018 10:55:58 +
From: "Gujjar, Abhinandan S"
To: Jerin Jacob
CC: "dev@dpdk.org" , "Vangati, Narender"
, "Rao, Nikhil" , "Eads,
Gage" , "hemant.agra...@nxp.com"
, "akhil.go...@nxp.com" ,
In case osal_dma_alloc_coherent() is called from a management thread,
core_id turn out to be LCORE_ID_ANY, and the resulting socket for alloc
will be socket 0.
This is not desirable when using a NIC from socket 1 which might very
likely be configured to use memory from that socket only.
In that ca
Hi,
Not sure why cover letter wasn’ t appended.
In some cases we require all packets (including the ones that ixgbe
considers as Rx length errors) to be received on backplane ixgbe port. The
proposed API sets the requisite SBP bit for ixgbe to receive Rx length
error packets.
If this is required
Thanks a lot for your suggestions,
Taking them into account and having a look a this example on userdata field
usage (http://dpdk.org/doc/api/examples_2bbdev_app_2main_8c-example.html#a19),
I have though the following plan. I think that the most elegant way to do
it is to use "userdata" for metada
On Wed, Feb 21, 2018 at 01:38:38PM +, Ophir Munk wrote:
> When creating an RSS flow with missing actions parameters, for example:
> flow create 0 ingress pattern / end actions rss / end
>
> testpmd aborts with segmentation fault.
> In the corrupted code mlx4_flow_prepare() accesses RSS actio
On Tue, Feb 20, 2018 at 05:07:27PM +, Bruce Richardson wrote:
> Following on from the number of patches needing to be done for strncpy
> issues highlighted by coverity...
>
> The strncpy function is error prone for doing "safe" string copies, so
> we generally try to use "snprintf" instead in
On Tue, Feb 20, 2018 at 6:07 PM, Bruce Richardson
wrote:
> Following on from the number of patches needing to be done for strncpy
> issues highlighted by coverity...
>
> The strncpy function is error prone for doing "safe" string copies, so
> we generally try to use "snprintf" instead in the code.
Hi Pavan,
> -Original Message-
> From: Pavan Nikhilesh [mailto:pbhagavat...@caviumnetworks.com]
> Sent: Friday, February 16, 2018 3:37 PM
> To: jerin.ja...@caviumnetworks.com;
> santosh.shu...@caviumnetworks.com; Carrillo, Erik G
>
> Cc: dev@dpdk.org; Pavan Nikhilesh
> Subject: [dpdk-dev
The current dynamic logging has some awkward user interface choices.
It uses integers for log levels which requires user to know the
mapping between numeric and symbolic values.
A bigger problem was the choice of regular expressions and option
format for dynamic logging. Dynamic log names are sepe
Much easeier to remember names than numbers. Allows
--log-level=pmd.net.ixgbe.*,debug
The option argument allow shortened form so
--log-level=pmd.net.ixgbe.*,i
also works.
Signed-off-by: Stephen Hemminger
---
lib/librte_eal/common/eal_common_options.c | 68 ++
Regular expressions are not the best way to match a hierarchal
pattern like dynamic log levels. And the seperator for dynamic
log levels is period which is the regex wildcard character.
A better solution is to use filename matching 'globbing' so
that log levels match like file paths. For compatiab
The use of dynamic log in documentation should use matching not
regex notation.
Signed-off-by: Stephen Hemminger
---
doc/guides/contributing/coding_style.rst | 2 +-
doc/guides/nics/qede.rst | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/guides/contrib
The current dynamic logging has some awkward user interface choices.
It uses integers for log levels which requires user to know the
mapping between numeric and symbolic values.
A bigger problem was the choice of regular expressions and option
format for dynamic logging. Dynamic log names are sepe
Much easeier to remember names than numbers. Allows
--log-level=pmd.net.ixgbe.*,debug
Signed-off-by: Stephen Hemminger
---
lib/librte_eal/common/eal_common_options.c | 66 ++
1 file changed, 50 insertions(+), 16 deletions(-)
diff --git a/lib/librte_eal/common
Regular expressions are not the best way to match a hierarchical
pattern like dynamic log levels. And the separator for dynamic
log levels is period which is the regex wildcard character.
A better solution is to use filename matching 'globbing' so
that log levels match like file paths. For compati
The use of dynamic log in documentation should use matching not
regex notation.
Signed-off-by: Stephen Hemminger
---
doc/guides/contributing/coding_style.rst | 2 +-
doc/guides/nics/qede.rst | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/guides/contrib
Hi Fiona,
Thanks for starting this discussion. In the current API the user must
make 12 API calls just to get information to compress. Maybe there is a
way to simplify. At least for some use cases (stateless). I think a call
sometime next week would be good to help clarify coalesce some of the
com
In some cases, we don't want to lock all memory.
Add an option --no-mlockall to avoid lock all memory.
Cc: wenzhuo...@intel.com
Cc: jingjing...@intel.com
Signed-off-by: Jianfeng Tan
---
app/test-pmd/parameters.c | 5 -
app/test-pmd/testpmd.c| 32 +++
In vhost-switch example, when binding nic to vfio-pci, dequeue zero
copy cannot work in VM2NIC mode due to no iommu dma mapping is setup
for guest memory currently.
Signed-off-by: Junjie Chen
---
doc/guides/sample_app_ug/vhost.rst | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff -
28 matches
Mail list logo
