Hi all,
during some tests with dpdk 18.02.2 on RedHat 7 kernel
3.10.0-862.el7.x86_64 using Intel X710 and 2 x Intel(R) Xeon(R) Gold
6130 CPU @ 2.10GHz I found the following.
I put some log in the function set_tsc_freq as you can see below
void
set_tsc_freq(void)
{
uint64_t freq;
has been
correctly set by the rte_eth_dev_configure function. Is this a bug or
something known about registers of X710?
Matteo
Il 02/10/2018 19:19, Matteo Lanzuisi ha scritto:
Hi all,
I got a huge problem: I found that using normal hashing and
configuration on X710 hardware is not sufficient
Hi all,
I got a huge problem: I found that using normal hashing and
configuration on X710 hardware is not sufficient, so I followed some
threads and read the code inside the testpmd application to configure a
symmetric hashing for IP src / IP dst on TCP packets so that all packets
in a flow a
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
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-linuxapp-gcc
I changed the SRC_IP and DST_IP this way
#define SRC_IP ((83<<24) + (175
hugepage management
changes between 2.2.0 and 17.07 dpdk version.
Thank you for you time and patience,
Matteo
Il 24/08/2018 18:47, Wiles, Keith ha scritto:
On Aug 24, 2018, at 9:44 AM, Matteo Lanzuisi wrote:
Hi,
I used valgrind again for a very long time, and it told me nothing strange is
// do something if result != 0 ...
}
}
else
{
// don't use mempool but call a function instead
}
}
and now it all goes well.
It is possibile that sending to itself could generate this issue?
Regards,
Matteo
Il 21/08/2018 16:46, Matteo Lanzuisi ha scritto:
I
Il 21/08/2018 14:51, Wiles, Keith ha scritto:
On Aug 21, 2018, at 7:44 AM, Matteo Lanzuisi wrote:
Il 21/08/2018 14:17, Wiles, Keith ha scritto:
On Aug 21, 2018, at 7:01 AM, Matteo Lanzuisi wrote:
Hi
Il 20/08/2018 18:03, Wiles, Keith ha scritto:
On Aug 20, 2018, at 9:47 AM, Matteo
Il 21/08/2018 14:17, Wiles, Keith ha scritto:
On Aug 21, 2018, at 7:01 AM, Matteo Lanzuisi wrote:
Hi
Il 20/08/2018 18:03, Wiles, Keith ha scritto:
On Aug 20, 2018, at 9:47 AM, Matteo Lanzuisi
wrote:
Hello Olivier,
Il 13/08/2018 23:54, Olivier Matz ha scritto:
Hello Matteo,
On Mon
Hi
Il 20/08/2018 18:03, Wiles, Keith ha scritto:
On Aug 20, 2018, at 9:47 AM, Matteo Lanzuisi wrote:
Hello Olivier,
Il 13/08/2018 23:54, Olivier Matz ha scritto:
Hello Matteo,
On Mon, Aug 13, 2018 at 03:20:44PM +0200, Matteo Lanzuisi wrote:
Any suggestion? any idea about this behaviour
Hello Olivier,
Il 13/08/2018 23:54, Olivier Matz ha scritto:
Hello Matteo,
On Mon, Aug 13, 2018 at 03:20:44PM +0200, Matteo Lanzuisi wrote:
Any suggestion? any idea about this behaviour?
Il 08/08/2018 11:56, Matteo Lanzuisi ha scritto:
Hi all,
recently I began using "dpdk-17.11-1
Any suggestion? any idea about this behaviour?
Il 08/08/2018 11:56, Matteo Lanzuisi ha scritto:
Hi all,
recently I began using "dpdk-17.11-11.el7.x86_64" rpm (RedHat rpm) on
RedHat 7.5 kernel 3.10.0-862.6.3.el7.x86_64 as a porting of an
application from RH6 to RH7. On RH6 I used
Hi all,
recently I began using "dpdk-17.11-11.el7.x86_64" rpm (RedHat rpm) on
RedHat 7.5 kernel 3.10.0-862.6.3.el7.x86_64 as a porting of an
application from RH6 to RH7. On RH6 I used dpdk-2.2.0.
This application is made up by one or more threads (each one on a
different logical core) readin
13 matches
Mail list logo
