DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH] doc: add release note entry for EAL lcores flag
Date: Tue, 10 Jun 2025 15:50:55 +0100	[thread overview]
Message-ID: <20250610145055.1497390-1-bruce.richardson@intel.com> (raw)

Add an entry in the release notes about the "-l" flag now being the
same as the "--lcores" flag. Refer to the GSG for examples.

Fixes: 1ea3833e9c4e ("eal: merge corelist and core mapping options")

Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
 doc/guides/rel_notes/release_25_07.rst | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/doc/guides/rel_notes/release_25_07.rst b/doc/guides/rel_notes/release_25_07.rst
index a5b353d342..fa44dc562a 100644
--- a/doc/guides/rel_notes/release_25_07.rst
+++ b/doc/guides/rel_notes/release_25_07.rst
@@ -55,6 +55,14 @@ New Features
      Also, make sure to start the actual text at the margin.
      =======================================================
 
+* **Enhanced EAL ``-l`` corelist argument.**
+
+  Added support to the EAL ``-l`` argument for the full range of core-to-cpu mapping options supported by the ``--lcores`` EAL argument.
+  Previously, ``-l`` only supported a subset of the options,
+  allowing only a list of cpus to be specified, which would be mapped 1:1 with internal lcore ids.
+  Now, it is possible to use the shortened ``-l`` form to map lcore ids to threads running on specific CPUs.
+  See the :doc:`../linux_gsg/eal_args.include` guide for examples.
+
 * **Added PMU library.**
 
   Added a Performance Monitoring Unit (PMU) library which allows Linux applications
-- 
2.48.1


             reply	other threads:[~2025-06-10 14:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 14:50 Bruce Richardson [this message]
2025-06-12  0:11 ` Thomas Monjalon

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=20250610145055.1497390-1-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).