From: Avi Kivity <avi@argo.co.il>
To: Andrew Morton <akpm@osdl.org>
Cc: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@timesys.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Arjan <arjan@linux.intel.com>
Subject: Re: [RFC][PATCH] Add do_not_call_when_idle option to timer and workqueue
Date: Wed, 22 Nov 2006 08:38:20 +0200 [thread overview]
Message-ID: <4563F05C.4090809@argo.co.il> (raw)
In-Reply-To: <20061121181114.b9d923bd.akpm@osdl.org>
Andrew Morton wrote:
>> Index: linux-2.6.19-rc-mm/include/linux/timer.h
>> ===================================================================
>> --- linux-2.6.19-rc-mm.orig/include/linux/timer.h 2006-11-13 15:06:26.000000000 -0800
>> +++ linux-2.6.19-rc-mm/include/linux/timer.h 2006-11-13 16:01:03.000000000 -0800
>> @@ -8,6 +8,8 @@
>>
>> struct tvec_t_base_s;
>>
>> +#define TIMER_FLAG_NOT_IN_IDLE (0x1)
>> +
>> struct timer_list {
>> struct list_head entry;
>> unsigned long expires;
>> @@ -16,6 +18,7 @@
>> unsigned long data;
>>
>> struct tvec_t_base_s *base;
>> + int flags;
>> #ifdef CONFIG_TIMER_STATS
>>
>
> Adding a new field to the timer_list is somewhat of a hit - this is going
> to make an awful lot of data structures a bit larger. Some of which we
> allocate a large number of.
>
> I think we could justfy getting nasty and using the LSB of
> timer_list.function for this..
>
>
The lsb of a function pointer is used in variable length instruction
processors (such as x86 when optimizing for size). The msb is constant
though.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2006-11-22 6:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 0:28 [RFC][PATCH] Add do_not_call_when_idle option to timer and workqueue Venkatesh Pallipadi
2006-11-22 2:11 ` Andrew Morton
2006-11-22 6:38 ` Avi Kivity [this message]
2006-11-22 8:50 ` Arjan van de Ven
2006-11-22 17:13 ` Venkatesh Pallipadi
2006-11-22 20:02 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4563F05C.4090809@argo.co.il \
--to=avi@argo.co.il \
--cc=akpm@osdl.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@timesys.com \
--cc=venkatesh.pallipadi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox