All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Anna-Maria Behnsen <anna-maria@linutronix.de>
Subject: Re: [PATCH] timers: Recalculate next timer interrupt only when necessary
Date: Thu, 23 Jul 2020 16:45:45 +0200	[thread overview]
Message-ID: <20200723144544.GC28401@lenoir> (raw)
In-Reply-To: <87a6zqxrqb.fsf@nanos.tec.linutronix.de>

On Thu, Jul 23, 2020 at 03:53:32PM +0200, Thomas Gleixner wrote:
> Frederic Weisbecker <frederic@kernel.org> writes:
> >
> > Since recalculating the next_expiry isn't a free operation, especially
> > when we must climb up the last wheel level to find out that no timer
> > has
> 
> I'm climbing stairs or mountains :)

Arguably, climbing a wheel can be a never ending story :)

> 
> > been enqueued at all, lets reuse the next expiry cache when it is
> > known
> 
> lets? Come on, the changelog is about facts not what we might do.

Also since you applied the last patchset I have tried to quit using "we"
in the changelog and use "the code" as a subject or even the passive form.
But reading above, I did it again.

Too many habits :))

> 
> >  	unsigned long		clk;
> >  	unsigned long		next_expiry;
> > +	bool			next_expiry_recalc;
> >  	unsigned int		cpu;
> >  	bool			is_idle;
> 
> Care to stare at the output of
> 
>      pahole -C timer_base kernel/time/timer.o
> 
> before and after?

Ah right, I'll move the bool together.

Thanks.

      reply	other threads:[~2020-07-23 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21  0:05 [PATCH] timers: Recalculate next timer interrupt only when necessary Frederic Weisbecker
2020-07-23 13:53 ` Thomas Gleixner
2020-07-23 14:45   ` Frederic Weisbecker [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=20200723144544.GC28401@lenoir \
    --to=frederic@kernel.org \
    --cc=anna-maria@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.