The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: johnstul@us.ibm.com
Cc: paulus@samba.org, linux-kernel@vger.kernel.org
Subject: Re: why do we have wall_jiffies?
Date: Fri, 03 Mar 2006 01:07:54 +0900 (JST)	[thread overview]
Message-ID: <20060303.010754.30187520.anemo@mba.ocn.ne.jp> (raw)
In-Reply-To: <1140202014.5479.4.camel@leatherman>

Oh, I missed this thread...

>>>>> On Fri, 17 Feb 2006 10:46:53 -0800, john stultz <johnstul@us.ibm.com> said:
>> In other places there is code that uses (jiffies - wall_jiffies).
>> However I can't see any way that jiffies and wall_jiffies could
>> ever be different (except for a few nanoseconds while executing the
>> code above).  I also can't see any way that `ticks' could ever be
>> anything other than 1.
>> 
>> Is the wall_jiffies stuff just a leftover from days when we used to
>> do timekeeping from a softirq?  Or am I missing something
>> fundamental?

john> Its only use right now is that on some arches we increment
john> jiffies when we detect lost ticks. This then forces xtime to be
john> updated the appropriate number of times.

Currently, jiffies and wall_jiffies is _really_ different most of
time.  The jiffies is almost always one bigger than wall_jiffies (at
least on i386 and MIPS).  Please refer my yesterday's mail (subject:
jiffies_64 vs. jiffies) for the reason.

john> It probably could be killed and the arches can just call
john> do_timer() the appropriate number of times. That might clean
john> some things up. My TOD work would also make it unnecessary.

I just posted a patch to doing this (subject: [PATCH] simplify
update_times ...).  I thought only x86_64 is doing such thing, right?

Also, I suppose then we can get rid of wall_jiffies completely.
---
Atsushi Nemoto

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-17  5:56 why do we have wall_jiffies? Paul Mackerras
2006-02-17 18:46 ` john stultz
2006-03-02 16:07   ` Atsushi Nemoto [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=20060303.010754.30187520.anemo@mba.ocn.ne.jp \
    --to=anemo@mba.ocn.ne.jp \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.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