Re: [patch 10/10] Scheduler profiling - Use immediate values

Alexey Dobriyan <[email protected]> writes:

> On Tue, Jul 03, 2007 at 12:40:56PM -0400, Mathieu Desnoyers wrote:
> > Use immediate values with lower d-cache hit in optimized version as a
> > condition for scheduler profiling call.
> 
> I think it's better to put profile.c under CONFIG_PROFILING as
> _expected_, so CONFIG_PROFILING=n users won't get any overhead, immediate or
> not. That's what I'm going to do after test-booting bunch of kernels.

No, it's better to handle this efficiently at runtime e.g. for 
distribution kernels. Mathieu's patch is good

-Andi
-
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 00/10] Immediate Values
    • From: Mathieu Desnoyers <[email protected]>
  • [patch 10/10] Scheduler profiling - Use immediate values
    • From: Mathieu Desnoyers <[email protected]>
  • Re: [patch 10/10] Scheduler profiling - Use immediate values
    • From: Alexey Dobriyan <[email protected]>

• Prev by Date: Re: [PATCH] Some love to default profiler
• Next by Date: Re: blink driver power saving
• Previous by thread: Re: [patch 10/10] Scheduler profiling - Use immediate values
• Next by thread: [patch 09/10] F00F bug fixup for i386 - use immediate values
• 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]