diff options
author | Pratyush Yadav <ptyadav@amazon.de> | 2023-09-12 17:52:49 +0200 |
---|---|---|
committer | Keith Busch <kbusch@kernel.org> | 2023-09-12 09:06:58 -0700 |
commit | dad651b2a44eb6b201738f810254279dca29d30d (patch) | |
tree | d640b134aaf8e1183e82b64c5b25fe4b38190028 /drivers/nvme | |
parent | 8ae5b3a685dc59a8cf7ccfe0e850999ba9727a3c (diff) |
nvme-pci: do not set the NUMA node of device if it has none
If a device has no NUMA node information associated with it, the driver
puts the device in node first_memory_node (say node 0). Not having a
NUMA node and being associated with node 0 are completely different
things and it makes little sense to mix the two.
Signed-off-by: Pratyush Yadav <ptyadav@amazon.de>
Signed-off-by: Keith Busch <kbusch@kernel.org>
Diffstat (limited to 'drivers/nvme')
-rw-r--r-- | drivers/nvme/host/pci.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c index baf69af7ea78..f5ba2d7102ea 100644 --- a/drivers/nvme/host/pci.c +++ b/drivers/nvme/host/pci.c @@ -2916,9 +2916,6 @@ static struct nvme_dev *nvme_pci_alloc_dev(struct pci_dev *pdev, struct nvme_dev *dev; int ret = -ENOMEM; - if (node == NUMA_NO_NODE) - set_dev_node(&pdev->dev, first_memory_node); - dev = kzalloc_node(sizeof(*dev), GFP_KERNEL, node); if (!dev) return ERR_PTR(-ENOMEM); |