On Thu, Mar 15, 2007 at 12:25:16AM -0700, David Miller wrote:
> Could we obtain %rip relative addressing with the ELF
> relocation approach I mentioned?
I think we can for some of the objects -- things like slab caches are
good candidates if we have the initialization done at init time, which
would actually be a very cool way of getting rid of the static slab
creation calls. I'll cook something better up on the slab front.
As for other variables, many can't be rip relative as they often end up
pointing to addresses outside of the +/-2GB range we have there.
The main reason I came up with this was from looking at the various
kprobes and notifier chain overhead in common code paths. In many
instances we need a single byte flag showing the feature is in use to
jump out of the hot path.
Then there are the selinux hooks....
-ben
--
"Time is of no importance, Mr. President, only life is important."
Don't Email: <[EMAIL PROTECTED]>.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
