2015-07-31 17:08, Thomas Monjalon:
> Can we enable ixgbe SSE on BSD?
> CONFIG_RTE_IXGBE_RX_OLFLAGS_DISABLE must be renamed to
> CONFIG_RTE_IXGBE_RX_OLFLAGS_ENABLE, or can we remove this option?
> Can we remove i40e bulk alloc option?
> Why IEEE1588 is disabled? Can we remove this option?
One more
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Friday, July 31, 2015 2:12 PM
> To: Zhang, Helin; Ananyev, Konstantin; Richardson, Bruce
> Cc: dev at dpdk.org
> Subject: [PATCH 3/3] config: remove kni options for bsd
>
> KNI is a Linux-only
I asked about this many months ago and was informed that "-1" is a "standard
error value" that I should expect from these APIs when NUMA is not present.
Now we're saying I have to change my code again to handle a zero value?
Also not sure how to tell the difference between no NUMA, something
2015-07-31 15:39, Zhang, Helin:
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> > 2015-07-31 15:29, Zhang, Helin:
> > > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> > > > Can we remove i40e bulk alloc option?
> > >
> > > As the receiving functions are different for
Hi Francesco,
2015-07-31 15:18, Montorsi, Francesco:
> I 'm attempting to integrate DPDK code in an existing application,
> which includes .
> That standard glibc header already provides a structure named ether_addr
Yes it's a known problem.
See http://dpdk.org/dev/patchwork/patch/2175/
2015-07-31 15:29, Zhang, Helin:
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> > Can we remove i40e bulk alloc option?
>
> As the receiving functions are different for bulk_alloc or not, we need this
> flag.
What brings the non bulk alloc function?
Why is it disabled for BSD?
Hi,
Currently most of the build options are duplicated in 2 config files.
They should be merged in a common file to avoid this kind of differences:
--- config/common_bsdapp
+++ config/common_linuxapp
-CONFIG_RTE_IXGBE_INC_VECTOR=n
+CONFIG_RTE_IXGBE_INC_VECTOR=y
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Friday, July 31, 2015 8:43 AM
> To: Zhang, Helin
> Cc: Ananyev, Konstantin; Richardson, Bruce; dev at dpdk.org
> Subject: Re: config files maintenance
>
> 2015-07-31 15:39, Zhang, Helin:
> > From:
The patch removes the restriction of burst size on a constant 32.
On receive side, the burst size floor now aligns to RTE_IXGBE_DESCS_PER_LOOP
power of 2.
According to this rule, the burst size less than 4 still won't receive anything.
(Before this change, the burst size less than 32 can't
On 31/07/15 12:57, Zoltan Kiss wrote:
>>
>> Another thing, that I just thought about:
>> Right now we invoke ixgbe_rxq_rearm() only at the start of
>> _recv_raw_pkts_vec().
>> Before it was ok, as _recv_raw_pkts_vec() would never try to read more
>> then 32 RXDs.
>> But what would happen if
Hi Thomas,
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Friday, July 31, 2015 4:08 PM
> To: Zhang, Helin; Ananyev, Konstantin; Richardson, Bruce
> Cc: dev at dpdk.org
> Subject: config files maintenance
>
> Hi,
>
> Currently most of the
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Friday, July 31, 2015 8:31 AM
> To: Zhang, Helin
> Cc: Ananyev, Konstantin; Richardson, Bruce; dev at dpdk.org
> Subject: Re: config files maintenance
>
> 2015-07-31 15:29, Zhang, Helin:
> > From:
> -Original Message-
> From: Jeff Venable, Sr. [mailto:jeff at vectranetworks.com]
> Sent: Wednesday, July 29, 2015 6:59 PM
> To: Zhang, Helin
> Cc: dev at dpdk.org; lhffjzh; 'Thomas Monjalon'
> Subject: RE: [dpdk-dev] Why only rx queue "0" can receive network packet by
> i40e NIC
>
>
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Friday, July 31, 2015 8:08 AM
> To: Zhang, Helin; Ananyev, Konstantin; Richardson, Bruce
> Cc: dev at dpdk.org
> Subject: config files maintenance
>
> Hi,
>
> Currently most of the build options
Hi all,
I 'm attempting to integrate DPDK code in an existing application, which
includes .
That standard glibc header already provides a structure named ether_addr
defined as:
struct ether_addr
{
u_int8_t ether_addr_octet[ETH_ALEN];
} __attribute__ ((__packed__));
So the result is that gcc
librte_pmd_mlx4.so needs to be linked with libibverbs otherwise, the PMD is
not able to open Mellanox devices and the following message is printed by
testpmd at startup
"librte_pmd_mlx4: cannot access device, is mlx4_ib loaded?".
Applications dependency on libibverbs are moved to be only valid in
Some .so libraries needs to be linked with external libraries. For that the
LDLIBS and EXTRA_LDFLAGS variables should be present on the link line when
those .so files are created. PMD Makefile is responsible for filling the
LDLIBS variable with the link to the external library it needs.
In Rx and Tx queue_disable functions, the index of queue should
be qnum other than i which is the iteration of time expiration.
When a Tx queue fails to start in fm10k_dev_start, all Rx queues
and Tx queues that are started should be cleaned before the
function returns an error.
Signed-off-by:
On 31/07/2015 12:39, John McNamara wrote:
> Fixes issue where ieee15888 timestamping doesn't work for the i40e
> pmd when RTE_ABI_NEXT is enabled.
>
> Also refactors repeated ieee15888 flag checking and setting
> code into a function.
>
> Reported-by: Huilong Xu
> Signed-off-by: John McNamara
>
On 31/07/15 11:21, Ananyev, Konstantin wrote:
>
>
>> -Original Message-
>> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Zoltan Kiss
>> Sent: Friday, July 31, 2015 11:04 AM
>> To: Liang, Cunming; dev at dpdk.org
>> Subject: Re: [dpdk-dev] [PATCH v1] ixgbe: remove vector pmd
Fixes issue where ieee15888 timestamping doesn't work for the i40e
pmd when RTE_ABI_NEXT is enabled.
Also refactors repeated ieee15888 flag checking and setting
code into a function.
Reported-by: Huilong Xu
Signed-off-by: John McNamara
---
v2: Fix for "unused function" warning with clang >=
On 31/07/15 09:17, Cunming Liang wrote:
> The patch removes the restriction of burst size on a constant 32.
>
> On receive side, the burst size floor now aligns to RTE_IXGBE_DESCS_PER_LOOP
> power of 2.
> According to this rule, the burst size less than 4 still won't receive
> anything.
>
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Zoltan Kiss
> Sent: Friday, July 31, 2015 11:04 AM
> To: Liang, Cunming; dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v1] ixgbe: remove vector pmd burst size
> restriction
>
>
>
> On 31/07/15 09:17,
The patch sets zero as the default value of pci device numa_node
if the socket could not be determined.
It provides the same default value as FreeBSD which has no NUMA support,
and makes the return value of rte_eth_dev_socket_id() be consistent
with the API description.
Signed-off-by: Cunming
> -Original Message-
> From: Liang, Cunming
> Sent: Friday, July 31, 2015 9:18 AM
> To: dev at dpdk.org
> Cc: Ananyev, Konstantin; Liang, Cunming
> Subject: [PATCH v1] ixgbe: remove vector pmd burst size restriction
>
> The patch removes the restriction of burst size on a constant 32.
>
Ieee1588 reads system time to set its timestamp. On 1G NICs, for example,
i350, system time is disabled by default. It means the ieee1588 timestamp
will always be 0.
This patch enables system time when ieee1588 is enabled.
v2 changes:
* move the macro to the top of the file with the other
> -Original Message-
> From: Neil Horman [mailto:nhorman at tuxdriver.com]
> Sent: Monday, July 13, 2015 3:00 PM
> To: Mcnamara, John
> Cc: dev at dpdk.org; vladz at cloudius-systems.com
> Subject: Re: [dpdk-dev] [PATCH] ethdev: fix ABI breakage in lro code
>
> On Mon, Jul 13, 2015 at
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Srikanth Akula
> Sent: Wednesday, July 29, 2015 10:32 PM
> To: dev at dpdk.org; dev at openvswitch.org
> Subject: [dpdk-dev] Fwd: OVS with DPDK ..Error packets
>
> (+DPDK dev team )
>
>
> Hello ,
>
> I am
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Wenzhuo Lu
> Sent: Friday, July 31, 2015 2:21 AM
> To: dev at dpdk.org
> Subject: [dpdk-dev] [PATCH v2] e1000: fix ieee1588 timestamp issue
>
> Ieee1588 reads system time to set its timestamp. On 1G NICs, for
On Fri, Jul 31, 2015 at 09:03:45AM +, Mcnamara, John wrote:
> > -Original Message-
> > From: Neil Horman [mailto:nhorman at tuxdriver.com]
> > Sent: Monday, July 13, 2015 3:00 PM
> > To: Mcnamara, John
> > Cc: dev at dpdk.org; vladz at cloudius-systems.com
> > Subject: Re: [dpdk-dev]
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Wang Xiao W
> Sent: Friday, July 31, 2015 1:06 PM
> To: dev at dpdk.org
> Cc: Wang, Xiao W
> Subject: [dpdk-dev] [PATCH] fm10k: fix 2 bugs in rxtx_queue_disable and
> fm10k_dev_start
>
> In Rx and Tx
Hi John,
> -Original Message-
> From: Mcnamara, John
> Sent: Thursday, July 30, 2015 5:59 PM
> To: Lu, Wenzhuo; dev at dpdk.org
> Subject: RE: [dpdk-dev] [PATCH] e1000: fix ieee1588 timestamp issue
>
> > -Original Message-
> > From: dev [mailto:dev-bounces at dpdk.org] On Behalf
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Cunming Liang
> Sent: Wednesday, July 29, 2015 10:05 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] [PATCH v3] doc: announce abi change for interrupt mode
>
> The patch announces the planned ABI changes for
33 matches
Mail list logo
