Re: [PATCH RFC V2 3/5] jump_label: if a key has already beeninitialized, don't nop it out
From: Steven Rostedt
Date: Thu Oct 06 2011 - 14:27:00 EST
On Thu, 2011-10-06 at 14:10 -0400, Jason Baron wrote:
> > Looks like jmp2 is about 5% faster than jmp5 on Sandybridge with this
> > benchmark.
> > But insignificant difference on Nehalem.
> > J
> It would be cool if we could make the total width 2-bytes, when
> possible. It might be possible by making the initial 'JUMP_LABEL_INITIAL_NOP'
> as a 'jmp' to the 'l_yes' label. And then patching that with a no-op at boot
> time or link time - letting the compiler pick the width. In that way we could
> get the optimal width...
Why not just do it?
jump_label is encapsulated in arch_static_branch() which on x86 looks
static __always_inline bool arch_static_branch(struct jump_label_key *key)
".pushsection __jump_table, \"aw\" \n\t"
_ASM_PTR "1b, %l[l_yes], %c0 \n\t"
: : "i" (key) : : l_yes);
That jmp to l_yes should easily be a two byte jump.
If not I'm sure it would be easy to catch it before modifying the code.
And then complain real loudly about it.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/