The message about constraining number of online cpus to be less than or
equal to ND_MAX_LANES (256) is only useful for block-aperture
configurations and BTT. Make it debug since its only relevant when
debugging performance.

Signed-off-by: Dan Williams <dan.j.willi...@intel.com>
---
 drivers/nvdimm/region.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/nvdimm/region.c b/drivers/nvdimm/region.c
index 034f0a07d627..b9ca0033cc99 100644
--- a/drivers/nvdimm/region.c
+++ b/drivers/nvdimm/region.c
@@ -27,10 +27,10 @@ static int nd_region_probe(struct device *dev)
        if (nd_region->num_lanes > num_online_cpus()
                        && nd_region->num_lanes < num_possible_cpus()
                        && !test_and_set_bit(0, &once)) {
-               dev_info(dev, "online cpus (%d) < concurrent i/o lanes (%d) < 
possible cpus (%d)\n",
+               dev_dbg(dev, "online cpus (%d) < concurrent i/o lanes (%d) < 
possible cpus (%d)\n",
                                num_online_cpus(), nd_region->num_lanes,
                                num_possible_cpus());
-               dev_info(dev, "setting nr_cpus=%d may yield better libnvdimm 
device performance\n",
+               dev_dbg(dev, "setting nr_cpus=%d may yield better libnvdimm 
device performance\n",
                                nd_region->num_lanes);
        }
 

Reply via email to