From: David Marchand <david.marchand@redhat.com>
To: Andre Muezerie <andremue@linux.microsoft.com>,
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] rcu: remove VLAs
Date: Fri, 16 May 2025 10:06:10 +0200 [thread overview]
Message-ID: <CAJFAV8yGcs6BTZbucSnM=ZkkPfOGWppp=YGrWr9XGZxtCnVW6Q@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8wyJLOCxKsZRNjVXvXwkOULz4TmLkwgWU=Sdar6iAfqzg@mail.gmail.com>
Hello,
On Thu, Apr 10, 2025 at 1:39 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> On Fri, Mar 7, 2025 at 2:40 AM Andre Muezerie
> <andremue@linux.microsoft.com> wrote:
> >
> > There are two lines that were using VLAs, which are not supported by
> > MSVC.
> >
> > 1)
> > ../lib/rcu/rte_rcu_qsbr.c:326:12: warning: variable length array used [-Wvla]
> > 326 | char data[dq->esize];
> > | ^~~~~~~~~
> > 2)
> > ../lib/rcu/rte_rcu_qsbr.c:389:12: warning: variable length array used [-Wvla]
> > 389 | char data[dq->esize];
> > | ^~~~~~~~~
> >
> > The short-term fix is to use alloca, to allow progress with the msvc
> > compatibility work.
> > The long-term plan involves API changes and therefore can only be applied
> > with a new release. This long-term plan consists of introducing some
> > reasonable limitation on RCU DQ element size.
> >
> > Signed-off-by: Andre Muezerie <andremue@linux.microsoft.com>
>
> Honnappa, any objection?
I'll take silence as a no.
Andre, you mention long-term plan, if you plan to do this change in
25.11, now would be a good time to prepare a deprecation notice on
this topic.
--
David Marchand
next prev parent reply other threads:[~2025-05-16 8:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 1:40 Andre Muezerie
2025-04-10 11:39 ` David Marchand
2025-05-16 8:06 ` David Marchand [this message]
2025-05-16 9:22 ` David Marchand
2025-05-16 13:09 ` Andre Muezerie
2025-05-16 13:30 ` David Marchand
2025-05-16 21:13 ` Andre Muezerie
2025-05-16 13:19 ` David Marchand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJFAV8yGcs6BTZbucSnM=ZkkPfOGWppp=YGrWr9XGZxtCnVW6Q@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=andremue@linux.microsoft.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).