Re: [patch 6/7] Unlinline a bunch of other functions

Arjan van de Ven <[email protected]> wrote:
>
>  Remove the "inline" keyword from a bunch of big functions in the kernel
>  with the goal of shrinking it by 30kb to 40kb

Was this done very carefully?  I look at e100_start_receiver() and cannot
see a reason for uninlining it.  Are there others?
-
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 1/7] Make __always_inline actually force always inlining
    • From: Arjan van de Ven <[email protected]>
  • [patch 6/7] Unlinline a bunch of other functions
    • From: Arjan van de Ven <[email protected]>

• Prev by Date: ext3 slab poison.
• Next by Date: Re: 2.6.15-mm1
• Previous by thread: Re: [patch 6/7] Unlinline a bunch of other functions
• Next by thread: [patch 3/7] mark several functions __always_inline
• 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]