RE: [PATCH] ia64: default the NUMA node distance when there is no ACPI SLIT

+	printk(KERN_INFO "Building NUMA distance from ACPI 2.0 SLIT\n");

This printk just looks like noise during boot.  Surely this
is normal behavior on a NUMA system?

+	printk(KERN_INFO "No SLIT table, defaulting NUMA distance\n");

But this one deserves more prominence than just KERN_INFO.  I'd
say that it deserves a KERN_ERR rating (without accurate information
we'll make some highly questionable scheduling and memory placement
decisions).  On the other hand the only way for the end-user to fix
this is to complain to their system vendor to fix firmware.  So perhaps
it is just a KERN_NOTICE.

-Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH] ia64: default the NUMA node distance when there is no ACPI SLIT
    • From: Andy Whitcroft <[email protected]>

• Prev by Date: Re: Regression in 2.6.23-rc2-mm2, mounting cpusets causes a hang
• Next by Date: Re: Thinking outside the box on file systems
• Previous by thread: [PATCH] ia64: default the NUMA node distance when there is no ACPI SLIT
• Next by thread: [PATCH] make attribute_container_unregister() unconditionally wait for list empty
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]