lkml.org 
[lkml]   [2004]   [Aug]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH][2.6] Completely out of line spinlocks / i386
On Wed, 11 Aug 2004, William Lee Irwin III wrote:
>> I actually favored making C language spin_lock() (i.e. the goddamn
>> thing is declared as a C function void spin_lock(spinlock_t *) and is
>> called like a normal C function -- no inline asm or inline C functions
>> at all) entrypoints beyond merely conslidating contention loops, but I
>> feared that would be too extreme of a reversal of the status quo to
>> ever get traction to post it. It did, however, shrink the kernel text
>> the most of any of the out-of-line spinlock patches by a large margin,
>> something completely absurd-sounding, like 220KB vs. 20KB-60KB. =)

On Wed, Aug 11, 2004 at 09:37:36PM -0400, Zwane Mwaikambo wrote:
> Could you post the patch and the results? It'd also be interesting to see
> the function call setup in a number of cases.

Odd, it was either you or mpm who told me the results. I personally
never even tried running the thing. I was merely told some other, prior
attempt at doing some kind of spinlock uninlining failed to run, this
thing did, and that it shaved that memorable amount off of .text size.
I recall I compiled it myself and saw about half as much reduction
(120KB instead of 220KB), possibly due to .config or compiler differences.
I'll dust things off and so on.

-- wli
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:05    [W:0.103 / U:3.832 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site