error: ‘for’ loop initial declarations are only allowed in C99 mode
Fixes: 609e79841fcf ("examples/l3fwd-power: add telemetry mode")
Cc: reshma.pat...@intel.com
Signed-off-by: Thomas Monjalon
---
examples/l3fwd-power/main.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/
The incriminated commit promoted those symbols as stable but the
prototypes still have the tag.
Fixes: 73eca2f77f4c ("devargs: promote experimental API as stable")
Cc: sta...@dpdk.org
Signed-off-by: David Marchand
Acked-by: Adrien Mazarguil
Acked-by: Stephen Hemminger
Acked-by: Neil Horman
--
The incriminated commit promoted this symbol as stable but the
prototype still has the tag.
Fixes: fb1a20331d70 ("raw/dpaa2_qdma: remove experimental tag from APIs")
Cc: sta...@dpdk.org
Signed-off-by: David Marchand
Acked-by: Adrien Mazarguil
Acked-by: Neil Horman
---
drivers/raw/dpaa2_qdma/r
This api was experimental and not properly marked in the map file.
But looking more closely, this is just an internal wrapper for EAL init.
Hide it in the hotplug code.
Fixes: 244d5130719c ("eal: enable hotplug on multi-process")
Cc: sta...@dpdk.org
Signed-off-by: David Marchand
Acked-by: Adrien
Here is a new series on __rte_experimental tags.
Following the build error reported by Aaron [1], I noticed that some
experimental functions could go unnoticed because of a gcc peculiarity.
To catch those, I went and added a new check on the object files to
ensure that any experimental api flagge
The incriminated commit promoted this symbol as stable but the
definition still has the tag.
Fixes: 787ae736a3d9 ("vfio: remove experimental tag")
Cc: sta...@dpdk.org
Signed-off-by: David Marchand
Acked-by: Adrien Mazarguil
Acked-by: Stephen Hemminger
Acked-by: Neil Horman
---
lib/librte_eal
Those symbols are declared in the library map but the prototypes are
missing the experimental tag.
Without it, existing users won't notice it is experimental.
Fixes: ec0dec44ecb9 ("net/atlantic: enable MACsec configuration")
Cc: sta...@dpdk.org
Signed-off-by: David Marchand
Acked-by: Adrien Maza
Fixes: 1b756087db93 ("telemetry: add parser for client socket messages")
Cc: sta...@dpdk.org
Signed-off-by: David Marchand
---
lib/librte_telemetry/rte_telemetry_parser.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/librte_telemetry/rte_telemetry_parser.c
b/lib/librte_telemetry/rte_t
This function is not visible from outside this code unit.
Fixes: 84e7477e10b1 ("mem: add thread unsafe version for DMA mask check")
Cc: sta...@dpdk.org
Signed-off-by: David Marchand
Acked-by: Adrien Mazarguil
Acked-by: Neil Horman
---
lib/librte_eal/common/eal_common_memory.c | 2 +-
1 file c
When promoting those symbols as stable, there is no check to ensure that
the final result is consistent.
Add a little script to get the symbols per section from the library map
files.
Validate that all experimental symbols in object files are referenced by
library map files.
Signed-off-by: David
We had some inconsistencies between functions prototypes and actual
definitions.
Let's avoid this by only adding the experimental tag to the prototypes.
Tests with gcc and clang show it is enough.
git grep -l __rte_experimental |grep \.c$ |while read file; do
sed -i -e '/^__rte_experimenta
Putting a '__attribute__((deprecated))' in the middle of a function
prototype does not result in the expected result with gcc (while clang
is fine with this syntax).
$ cat deprecated.c
void * __attribute__((deprecated)) incorrect() { return 0; }
__attribute__((deprecated)) void *correct(void) { re
28/06/2019 20:54, David Marchand:
> On Fri, Jun 28, 2019 at 8:44 PM Honnappa Nagarahalli <
> honnappa.nagaraha...@arm.com> wrote:
>
> > num_cores is of type uint8_t. This results in the following
> > compilation error.
> >
> > test_rcu_qsbr_perf.c:649:16: error: comparison is always false
> > due
29/06/2019 10:55, Thomas Monjalon:
> error: ‘for’ loop initial declarations are only allowed in C99 mode
>
> Fixes: 609e79841fcf ("examples/l3fwd-power: add telemetry mode")
> Cc: reshma.pat...@intel.com
>
> Signed-off-by: Thomas Monjalon
Applied quickly in the hope of getting CI in a stable st
28/06/2019 23:08, Mattias Rönnblom:
> When seeding the pseudo-random number generator, replace the 64-bit
> RDSEED with two 32-bit RDSEED instructions to allow building and
> running on 32-bit x86.
>
> Fixes: faf8fd252785 ("eal: improve entropy for initial PRNG seed")
>
> Reported-by: Ferruh Yigi
29/06/2019 13:58, David Marchand:
> Special mention for rte_mbuf_data_addr_default():
>
> There is either a bug or a (not yet understood) issue with gcc.
> gcc won't drop this inline when unused and rte_mbuf_data_addr_default()
> calls rte_mbuf_buf_addr() which itself is experimental.
> This resul
On Sat, Jun 29, 2019 at 6:14 PM Thomas Monjalon wrote:
> 29/06/2019 13:58, David Marchand:
> > Special mention for rte_mbuf_data_addr_default():
> >
> > There is either a bug or a (not yet understood) issue with gcc.
> > gcc won't drop this inline when unused and rte_mbuf_data_addr_default()
> >
29/06/2019 13:58, David Marchand:
> Following the build error reported by Aaron [1], I noticed that some
> experimental functions could go unnoticed because of a gcc peculiarity.
>
> To catch those, I went and added a new check on the object files to
> ensure that any experimental api flagged in t
>
> As a general remark consider writing all of the tbl entries including
> tbl8 with atomic_store. Now "lpm->tbl8[j] = new_tbl8_entry;" is looks like
>
> 1e9: 44 88 9c 47 40 01 00 mov
> %r11b,0x2000140(%rdi,%rax,2) <-write first byte
> 1f0: 02
> 1f1: 48 8
07/06/2019 10:32, David Marchand:
> On Thu, Jun 6, 2019 at 12:03 PM Ilya Maximets
> wrote:
>
> > According to API, 'rte_dev_probe()' and 'rte_dev_remove()' must
> > return 0 or negative error code. Bus code returns positive values
> > if device wasn't recognized by any driver, so the result of
>
Hi Ivan,
I'm curious about the alignment of your commit logs.
How do you manage to fit in such a beautiful alignment?
Is it a challenge to win something? :)
References:
http://dpdk.org/commit/42319ff3e0
http://dpdk.org/commit/64efa6f85d
http://dpdk.org/commit/f5f93e106e
Hi,
I am trying to set jumbo MTU on vmxnet3 but I see that
rte_eth_dev_set_mtu() is not implemented by the vmxnet3 drivers. Is
there any other way to set it?
Hi Andy:
> -Original Message-
> From: Pei, Andy
> Sent: Friday, June 21, 2019 5:23 PM
> To: dev@dpdk.org
> Cc: Pei, Andy ; Zhang, Helin ;
> sta...@dpdk.org; Zhang, Roy Fan ; Zhang, Qi Z
> ; Wu, Jingjing ; Xing, Beilei
> ; Yigit, Ferruh ; Xu, Rosen
> ; Ye, Xiaolong
> Subject: [PATCH v3] ne
> -Original Message-
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Xu, Rosen
> Sent: Thursday, June 27, 2019 6:44 PM
> To: Wei, Dan ; dev@dpdk.org
> Cc: Yigit, Ferruh ; Chen, Santos
> ; sta...@dpdk.org
> Subject: Re: [dpdk-dev] [DPDK v3] net/ipn3ke: modifications on AFU
> config
> -Original Message-
> From: Pei, Andy
> Sent: Friday, June 28, 2019 4:33 PM
> To: dev@dpdk.org
> Cc: Pei, Andy ; Zhang, Qi Z ; Wu,
> Jingjing ; Xing, Beilei ; Yigit,
> Ferruh ; Xu, Rosen ; Ye,
> Xiaolong ; Zhang, Roy Fan
> ; sta...@dpdk.org
> Subject: [PATCH v2] net/i40e: i40e get link
https://bugs.dpdk.org/show_bug.cgi?id=114
Mattias Rönnblom (mattias.ronnb...@ericsson.com) changed:
What|Removed |Added
Resolution|--- |FIXED
26 matches
Mail list logo
