From: john stultz <johnstul@us.ibm.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/2] Dynamic Tick: Enabling longer sleep times on 32-bit machines
Date: Wed, 11 Nov 2009 14:37:21 -0800 [thread overview]
Message-ID: <1257979042.3100.88.camel@localhost.localdomain> (raw)
In-Reply-To: <4AFB2547.7080008@ti.com>
On Wed, 2009-11-11 at 14:57 -0600, Jon Hunter wrote:
> john stultz wrote:
> > I could have sworn this was in mainline by now, but I recently was
> > looking for the code and can't find it there or in -tip either.
> >
> > Thomas, are they just hiding somewhere I can't find?
> >
> > Jon, you've been terribly patient and great about resubmitting these
> > patches over and over. If I'm not just being crazy and missing these
> > patches in front of my nose, are you still willing to submit them
> > again? I think they'll be quite useful as folks start pushing the NOHZ
> > idle times out.
>
> Absolutely! It is still on my to-do list, but unfortunately, I got busy
> with a couple other things.
>
> With regard to the last patch set I submitted for this, Thomas had an
> issue with one of the patches. I understand the concern, but I am not
> sure which would be the preferred way to handle this. See the below thread:
>
> http://marc.info/?l=linux-kernel&m=125062817124381&w=2
>
> If you or Thomas have any feedback on this, I could re-work the patch
> against the latest kernel tree.
Ok. I think Thomas is right there, setting the expiration to
max_time_delta makes the most sense. Honestly I suspect we don't ever
hit that case in the current code (no timers for 12 days), so its
probably an untested code path as it stands.
thanks
-john
next prev parent reply other threads:[~2009-11-11 22:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 17:45 [PATCH 0/2] Dynamic Tick: Enabling longer sleep times on 32-bit machines Jon Hunter
2009-08-18 17:45 ` [PATCH 1/2] Dynamic Tick: Prevent clocksource wrapping during idle Jon Hunter
2009-08-18 17:45 ` [PATCH 2/2] Dynamic Tick: Allow 32-bit machines to sleep for more than 2.15 seconds Jon Hunter
2009-08-18 19:26 ` Thomas Gleixner
2009-08-18 20:52 ` Jon Hunter
2009-11-13 19:50 ` [tip:timers/core] nohz: " tip-bot for Jon Hunter
2009-08-18 19:25 ` [PATCH 1/2] Dynamic Tick: Prevent clocksource wrapping during idle Thomas Gleixner
2009-08-18 20:42 ` Jon Hunter
2009-11-13 19:49 ` [tip:timers/core] nohz: " tip-bot for Jon Hunter
2009-11-11 20:43 ` [PATCH 0/2] Dynamic Tick: Enabling longer sleep times on 32-bit machines john stultz
2009-11-11 20:57 ` Jon Hunter
2009-11-11 22:37 ` john stultz [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-27 14:48 Jon Hunter
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=1257979042.3100.88.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=jon-hunter@ti.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox