mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Cc: 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 12:02:29 -0800	[thread overview]
Message-ID: <20061122120229.7218802d.akpm@osdl.org> (raw)
In-Reply-To: <20061122091324.A29862@unix-os.sc.intel.com>

On Wed, 22 Nov 2006 09:13:24 -0800
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com> wrote:

> On Tue, Nov 21, 2006 at 06:11:14PM -0800, Andrew Morton wrote:
> > On Tue, 21 Nov 2006 16:28:45 -0800
> > Venkatesh Pallipadi <venkatesh.pallipadi@intel.com> wrote:
> > 
> > > 
> > >  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..
> 
> That is a clever idea... Is that going to work in all architectures with all
> compiler flags?

Don't know.  Possibly not.  Other options are list.next, list.prev and
base.  None of them are pleasant.

      reply	other threads:[~2006-11-22 20:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22  0:28 Venkatesh Pallipadi
2006-11-22  2:11 ` Andrew Morton
2006-11-22  6:38   ` Avi Kivity
2006-11-22  8:50     ` Arjan van de Ven
2006-11-22 17:13   ` Venkatesh Pallipadi
2006-11-22 20:02     ` Andrew Morton [this message]

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=20061122120229.7218802d.akpm@osdl.org \
    --to=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

all inboxes | Powered by JetHome®