Re: [patch 4/7] Mark some key VFS functions as __always_inline

On Fri, Jan 06, 2006 at 11:41:12AM +0100, Arjan van de Ven wrote:
> From: Arjan van de Ven <[email protected]>
> 
> Mark a few VFS functions as mandatory inline (based on Al Viro's
> request); these must be inline due to stack usage issues during a recursive loop
> that happens during the recursive symlink resolution (symlink to a symlink to 
> a symlink ..)
> This patch at this point does not change behavior and is for documentation purposes
> only (but this changes later in the series)
> 
> 
> Signed-off-by: Arjan van de Ven <[email protected]>
> Signed-off-by: Ingo Molnar <[email protected]>
 
ACK
-
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 4/7] Mark some key VFS functions as __always_inline
    • From: Arjan van de Ven <[email protected]>

• Prev by Date: [patch 3/7] mark several functions __always_inline
• Next by Date: Re: [Bcm43xx-dev] [Fwd: State of the Union: Wireless]
• Previous by thread: [patch 4/7] Mark some key VFS functions as __always_inline
• Next by thread: [patch 7/7] Make "inline" no longer mandatory for gcc 4.x
• 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]