DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Cc: dev@dpdk.org, "Tyler Retzlaff" <roretzla@linux.microsoft.com>,
	"Chengwen Feng" <fengchengwen@huawei.com>,
	"Konstantin Ananyev" <konstantin.ananyev@huawei.com>,
	"Stephen Hemminger" <stephen@networkplumber.org>,
	"Morten Brørup" <mb@smartsharesystems.com>,
	"David Marchand" <david.marchand@redhat.com>,
	"Mattias Rönnblom" <hofors@lysator.liu.se>
Subject: Re: [PATCH] eal: fix lcore variables documentation
Date: Mon, 18 Nov 2024 19:16:24 +0100	[thread overview]
Message-ID: <3583431.V25eIC5XRa@thomas> (raw)
In-Reply-To: <82fc429d-8a0a-4c51-a68d-90eb7e4cc397@lysator.liu.se>

17/11/2024 20:11, Mattias Rönnblom:
> On 2024-11-14 18:09, Thomas Monjalon wrote:
> > The lcore variables API is new in DPDK 24.11,
> > that's why the function rte_lcore_var_alloc() was marked experimental.
> > To be clearer, the whole header file (including all macros)
> > is marked experimental.
> > 
> > A change decreased the default buffer size from 1 MB to 128 kB,
> > missing to update the documentation, which is fixed here.
> > 
> > Fixes: 5bce9bed67ad ("eal: add static per-lcore memory allocation facility")
> > Fixes: f2fd6c2e080c ("config: limit lcore variable maximum size to 128k")
> > 
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> 
> Acked-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com>

Applied




      reply	other threads:[~2024-11-18 18:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14 17:09 Thomas Monjalon
2024-11-17 19:11 ` Mattias Rönnblom
2024-11-18 18:16   ` Thomas Monjalon [this message]

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=3583431.V25eIC5XRa@thomas \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=hofors@lysator.liu.se \
    --cc=konstantin.ananyev@huawei.com \
    --cc=mattias.ronnblom@ericsson.com \
    --cc=mb@smartsharesystems.com \
    --cc=roretzla@linux.microsoft.com \
    --cc=stephen@networkplumber.org \
    /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).