[PATCH] test: raise fast test timeout to 60s on RISC-V

[Eric Long]

Current RISC-V hardware (e.g. HiFive Unmatched) is still way too slow
compared to other architectures' counterparts. On the most powerful
RISC-V CPU available (SG2042), DPDK still fails with 4 timeouts:

```
Summary of Failures:

23/77 DPDK:fast-tests / eventdev_selftest_swTIMEOUT
10.06s   killed by signal 15 SIGTERM
56/77 DPDK:fast-tests / rib6_autotest   TIMEOUT
10.04s
64/77 DPDK:fast-tests / spinlock_autotest   TIMEOUT
10.06s   killed by signal 15 SIGTERM
66/77 DPDK:fast-tests / table_autotest  TIMEOUT
11.28s   killed by signal 15 SIGTERM
```

On HiFive Unmatched, the longest test takes 53 seconds:

```
37/77 DPDK:fast-tests / lpm6_autotest   OK
53.29s
```

Raising timeout to 60s on RISC-V target will help test effectiveness
on it.

Signed-off-by: Eric Long 
---
 .mailmap| 1 +
 app/test/suites/meson.build | 5 +
 2 files changed, 6 insertions(+)

diff --git a/.mailmap b/.mailmap
index 7334ad58a9..24f3f4a0cd 100644
--- a/.mailmap
+++ b/.mailmap
@@ -404,6 +404,7 @@ Erez Ferber  
 Erez Shitrit 
 Eric Joyner 
 Eric Kinzie  
+Eric Long 
 Eric Zhang 
 Erik Gabriel Carrillo 
 Erik Ziegenbalg 
diff --git a/app/test/suites/meson.build b/app/test/suites/meson.build
index 191702cf76..b74d1c4ad7 100644
--- a/app/test/suites/meson.build
+++ b/app/test/suites/meson.build
@@ -6,6 +6,11 @@
 timeout_seconds = 600
 timeout_seconds_fast = 10
 
+if arch_subdir == 'riscv'
+# Current RISC-V machines are too slow to finish fast tests under 10s
+timeout_seconds_fast = 60
+endif
+
 test_no_huge_args = ['--no-huge', '-m', '2048']
 has_hugepage = run_command(has_hugepages_cmd, check: true).stdout().strip() != 
'0'
 message('hugepage availability: @0@'.format(has_hugepage))
-- 
2.47.0

igc dpdk driver for the Intel i225 and PHY_ID check

[David Hendel]

Hi,
I was told by an Intel representative which I am working on an issue related to 
the igc driver for the Intel 1225 chip with change in the PHY_ID and a check 
that DPDK igc driver is doing to this PHY_ID.

What is the right process to get an issue in the DPDK org? and get answers / 
change or fix to the driver.

Thanks, David.

David Hendel | Silicom | Office:+972-9-7644544 | Mobile: +972-54-5220122 | 
Email: da...@silicom.co.il