[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090108.205933.96892305.davem@davemloft.net>
Date: Thu, 08 Jan 2009 20:59:33 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: torvalds@...ux-foundation.org
Cc: hpa@...or.com, mingo@...e.hu, chris.mason@...cle.com,
peterz@...radead.org, rostedt@...dmis.org,
paulmck@...ux.vnet.ibm.com, ghaskins@...ell.com, matthew@....cx,
andi@...stfloor.org, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-btrfs@...r.kernel.org, tglx@...utronix.de, npiggin@...e.de,
pmorreale@...ell.com, SDietrich@...ell.com
Subject: Re: [PATCH -v7][RFC]: mutex: implement adaptive spinning
From: Linus Torvalds <torvalds@...ux-foundation.org>
Date: Thu, 8 Jan 2009 19:46:30 -0800 (PST)
> First off, gcc _does_ have a perfectly fine notion of how heavy-weight an
> "asm" statement is: just count it as a single instruction (and count the
> argument setup cost that gcc _can_ estimate).
Actually, at least at one point, it counted the number of newline
characters in the assembly string to estimate how many instructions
are contained inside.
It actually needs to know exaclty how many instructions are in there,
to emit proper far branches and stuff like that, for some cpus.
Since they never added an (optional) way to actually tell the compiler
this critical piece of information, so I guess the newline hack is the
best they could come up with.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists