[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 07 Jul 2011 19:20:20 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: Jason Baron <jbaron@...hat.com>
Cc: Ingo Molnar <mingo@...e.hu>, Paul Turner <pjt@...gle.com>,
linux-kernel@...r.kernel.org,
Bharata B Rao <bharata@...ux.vnet.ibm.com>,
Dhaval Giani <dhaval.giani@...il.com>,
Balbir Singh <balbir@...ux.vnet.ibm.com>,
Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com>,
Srivatsa Vaddagiri <vatsa@...ibm.com>,
Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>,
Pavel Emelyanov <xemul@...nvz.org>,
Hu Tao <hutao@...fujitsu.com>
Subject: Re: [patch 00/17] CFS Bandwidth Control v7.1
On Thu, 2011-07-07 at 12:23 -0400, Jason Baron wrote:
> yes, this is the type of case jump labels is designed for. Let me know
> if there are any usage questions/concerns.
Unrelated to this change, I was looking at a case where it would be nice
to have a way to specify the initial state of jump labels.
That is, currently:
jump_label_key foo;
if (static_branch(&foo))
will default to false, until jump_label_inc(&foo) etc..
I was looking to add something like:
jump_label_key foo = JUMP_LABEL_TRUE;
Which would initialize the thing to be true, the problem with that is
that it takes until the loop in jump_label_init() before that takes
effect, which was too late in my particular case.
Anyway, not the current problem and probably not your problem anyway,
but I wanted to throw the issue out there.
--
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