All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: dev@dpdk.org, Ray Kinsella <mdr@ashroe.eu>,
	David Marchand <david.marchand@redhat.com>,
	bruce.richardson@intel.com
Subject: Re: [PATCH] doc: announce behavior change for device NUMA node field
Date: Fri, 15 Jul 2022 18:07:57 +0200	[thread overview]
Message-ID: <2188818.iZASKD2KPV@thomas> (raw)
In-Reply-To: <20220713155043.11490-1-olivier.matz@6wind.com>

13/07/2022 17:50, Olivier Matz:
> 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>

    Acked-by: Bruce Richardson <bruce.richardson@intel.com>
    Acked-by: Jerin Jacob <jerinj@marvell.com>
    Acked-by: David Marchand <david.marchand@redhat.com>
    Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>

Applied with a bit of rewording as suggested by Bruce.



      parent reply	other threads:[~2022-07-15 16:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 15:50 [PATCH] doc: announce behavior change for device NUMA node field Olivier Matz
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 [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=2188818.iZASKD2KPV@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=mdr@ashroe.eu \
    --cc=olivier.matz@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.