DPDK patches and discussions
 help / color / mirror / Atom feed
From: Olivier Matz <olivier.matz@6wind.com>
To: dev@dpdk.org
Cc: Ray Kinsella <mdr@ashroe.eu>, David Marchand <david.marchand@redhat.com>
Subject: [PATCH] doc: announce behavior change for device NUMA node field
Date: Wed, 13 Jul 2022 17:50:43 +0200	[thread overview]
Message-ID: <20220713155043.11490-1-olivier.matz@6wind.com> (raw)

The dev->device.numa_node field is set by the bus driver for each device
it manages to indicate on which NUMA node this device lies.

When this information is unknown, the assigned value is not consistent
across the bus drivers. In v22.11, the value will be set to -1 in
this case.

Link: https://patches.dpdk.org/project/dpdk/patch/20211026090610.10823-1-houssem.bouhlel@6wind.com/

Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
---
 doc/guides/rel_notes/deprecation.rst | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 4e5b23c53d..5f269bf527 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -125,3 +125,9 @@ Deprecation Notices
   applications should be updated to use the ``dmadev`` library instead,
   with the underlying HW-functionality being provided by the ``ioat`` or
   ``idxd`` dma drivers
+
+* bus: The ``dev->device.numa_node`` field is set by the bus driver for
+  each device it manages to indicate on which NUMA node this device
+  lies. When this information is unknown, the assigned value is not
+  consistent across the bus drivers. In v22.11, the value will be set
+  to -1 in this case.
-- 
2.30.2


             reply	other threads:[~2022-07-13 15:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 15:50 Olivier Matz [this message]
2022-07-14 10:10 ` Bruce Richardson
2022-07-14 10:36   ` Jerin Jacob
2022-07-14 11:55 ` David Marchand
2022-07-14 12:03 ` Burakov, Anatoly
2022-07-15 16:07 ` 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=20220713155043.11490-1-olivier.matz@6wind.com \
    --to=olivier.matz@6wind.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=mdr@ashroe.eu \
    /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).