Re: [patch 0/3] Allow inlined spinlocks again V3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Date: Fri, 14 Aug 2009 14:10:45 -0700 (PDT)

> On Fri, 14 Aug 2009, Linus Torvalds wrote:
>> 
>> But not inline in the code, though. So yeah, it has a memory footprint, 
>> but shouldn't have a cache footprint.
> 
> An example of this: stack usage. This is the code with BUG_ON():
 ...
> and note how in the code, we're just jumping over something like four
> bytes ("ud2" plus that silly endless loop-jump just to make gcc happy
> are both 2 bytes on x86[-64]). 
> 
> Here's the same code with that horrid skb_under_panic():

Yes on x86 it's better even with verbose debugging because
of the inlining of the debug message pointer etc.

I'll have to do something more intelligent than I currently do on
sparc64, and I had always been meaning to do that. :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Kernel Newbies]     [x86 Platform Driver]     [Netdev]     [Linux Wireless]     [Netfilter]     [Bugtraq]     [Linux Filesystems]     [Yosemite Discussion]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]

  Powered by Linux