RE: Variation in measure_migration_cost() with scheduler-cache-hot-autodetect.patch in -mm

• To: "Chen, Kenneth W" <[email protected]>, "Ingo Molnar" <[email protected]>, <[email protected]>, <[email protected]>
• Subject: RE: Variation in measure_migration_cost() with scheduler-cache-hot-autodetect.patch in -mm
• From: "Luck, Tony" <[email protected]>
• Date: Tue, 21 Jun 2005 21:53:35 -0700
• Sender: [email protected]
• Thread-index: AcV22TLEFdKtCI6xSZCyAOFjzvSYuQADPGUg
• Thread-topic: Variation in measure_migration_cost() with scheduler-cache-hot-autodetect.patch in -mm

Nitpick: 

> 		printk("could not vmalloc %d bytes for cache!\n", 2*max_size);

You should change this printk() message to not say "vmalloc".

-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/

---

• Prev by Date: Re: [PATCH] devfs: remove devfs from Kconfig preventing it from being built
• Next by Date: [PATCH] w1: fix build issues
• Previous by thread: RE: Variation in measure_migration_cost() with scheduler-cache-hot-autodetect.patch in -mm
• Next by thread: [patch] spinlock cleanup
• 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]