mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: john stultz <johnstul@us.ibm.com>
Cc: zippel@linux-m68k.org, anemo@mba.ocn.ne.jp,
	clameter@engr.sgi.com, linux-kernel@vger.kernel.org,
	ralf@linux-mips.org, ak@muc.de
Subject: Re: [PATCH] simplify update_times (avoid jiffies/jiffies_64 aliasing problem)
Date: Fri, 3 Mar 2006 13:15:14 -0800	[thread overview]
Message-ID: <20060303131514.39e01dcb.akpm@osdl.org> (raw)
In-Reply-To: <1141417048.9727.60.camel@cog.beaverton.ibm.com>

john stultz <johnstul@us.ibm.com> wrote:
>
> But again, you're concerns are valid, there appears to be a lack of
>  enthusiasm in the community both for and against the changes. And I
>  understand, as I've got lots of other things I need to do as well, and
>  reviewing a large change like this can take some time that I'm sure
>  folks are short on.
> 
>  Maybe I should work on selling it more, I just have been at it for so
>  long with this patch set that I feel I'm boring folks with the constant
>  and repetitive "provides robust behavior in the face of lost ticks and
>  enables other development like high-res timers and realtime" schtick.
>

I'm not particularly worried from the will-it-break-the-kernel POV.  Any
remaining problems will affect a relatively small number of machines and
once the proverbial million monkeys start running it, things will be shaken
out of the current x86 implementation.

So we can do this, but the question is do we _want_ to do it?  If the arch
maintainers can look at it from a high level and say "yup, I can use that
and it'll improve/simplify/speedup/reduce my code" then yes, it's worth
making the effort.

It's a hard one.

  reply	other threads:[~2006-03-03 21:16 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-02 14:02 Atsushi Nemoto
2006-03-02 15:51 ` Atsushi Nemoto
2006-03-02 19:09 ` Christoph Lameter
2006-03-03  2:44   ` Atsushi Nemoto
2006-03-03  3:04     ` Andrew Morton
2006-03-03  3:20       ` Andi Kleen
2006-03-03  4:31       ` Atsushi Nemoto
2006-03-03  5:45         ` David S. Miller
2006-03-03 16:26           ` Atsushi Nemoto
2006-03-03 16:31         ` Atsushi Nemoto
2006-03-04  8:18           ` Andrew Morton
2006-03-04 11:20             ` Andi Kleen
2006-03-04 11:40               ` Andrew Morton
2006-03-04  5:21                 ` Andi Kleen
2006-03-04 23:13                 ` Paul Mackerras
2006-03-06  2:32                   ` Atsushi Nemoto
2006-03-04 11:42               ` Paul Mackerras
2006-03-04 11:44                 ` Andrew Morton
2006-03-04 12:33                   ` Paul Mackerras
2006-03-04 16:43                     ` Atsushi Nemoto
2006-03-03 20:17       ` john stultz
2006-03-03 21:15         ` Andrew Morton [this message]
2006-03-04 17:15         ` Atsushi Nemoto
2006-07-30 14:54           ` Atsushi Nemoto
2006-07-31 10:36             ` Martin Schwidefsky
2006-08-01 14:44               ` Atsushi Nemoto
2006-08-02 12:50                 ` Martin Schwidefsky
2006-08-03 15:53                   ` Atsushi Nemoto
2006-08-04 14:02                     ` Martin Schwidefsky
2006-08-06 16:13                       ` Atsushi Nemoto
2006-08-07 11:28                         ` Martin Schwidefsky
2006-08-07 19:58                         ` Andrew Morton
2006-08-08  8:11                           ` Martin Schwidefsky
2006-08-09 15:07                           ` Atsushi Nemoto
2006-03-03 18:13     ` john stultz
2006-03-04  2:34       ` Ralf Baechle

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=20060303131514.39e01dcb.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ak@muc.de \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=clameter@engr.sgi.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=zippel@linux-m68k.org \
    /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

Powered by JetHome