LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Dave Young" <hidave.darkstar@gmail.com>
To: "KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	hannes@saeurebad.de, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH v3] Add time_is_after_jiffies and others which compare with jiffies
Date: Tue, 11 Mar 2008 12:51:29 +0800	[thread overview]
Message-ID: <a8e1da0803102151y125f497x4d7fd57374c59b29@mail.gmail.com> (raw)
In-Reply-To: <20080311121553.6214.KOSAKI.MOTOHIRO@jp.fujitsu.com>

On Tue, Mar 11, 2008 at 11:17 AM, KOSAKI Motohiro
<kosaki.motohiro@jp.fujitsu.com> wrote:
> Hi
>
>  Why don't you make jiffies_64 stuff?

Actually, I greped the kernel source, and found none of time_*64 usage.

After grep again, I found a missed one in:
arch/x86/kernel/cpu/mcheck/therm_throt.c

        if (time_before64(tmp_jiffs, __get_cpu_var(next_check)))
                return 0;

Does it really need time_before64 here?

If it does need then I wonder whether the other 64 macros may be
removed, or just to add a time_is_before64_jiffies

>
>
>
>
>
>  > Most of time_after like macros usages just compare jiffies and
>  > another number, so here add some time_is_* macros for convenience.
>  >
>  > Signed-off-by: Dave Young <hidave.darkstar@gmail.com>
>  >
>  > ---
>  > include/linux/jiffies.h |   16 ++++++++++++++++
>  > 1 file changed, 16 insertions(+)
>  >
>  > diff -upr linux/include/linux/jiffies.h linux.new/include/linux/jiffies.h
>  > --- linux/include/linux/jiffies.h     2008-03-07 10:40:04.000000000 +0800
>  > +++ linux.new/include/linux/jiffies.h 2008-03-10 09:11:36.000000000 +0800
>  > @@ -135,6 +135,22 @@ static inline u64 get_jiffies_64(void)
>  >  #define time_before_eq64(a,b)        time_after_eq64(b,a)
>  >
>  >  /*
>  > + * These four macros compare jiffies and 'a' for convenience.
>  > + */
>  > +
>  > +/* time_is_before_jiffies(a) return true if a is before jiffies */
>  > +#define time_is_before_jiffies(a) time_after(jiffies, a)
>  > +
>  > +/* time_is_after_jiffies(a) return true if a is after jiffies */
>  > +#define time_is_after_jiffies(a) time_before(jiffies, a)
>  > +
>  > +/* time_is_before_eq_jiffies(a) return true if a is before or equal to jiffies*/
>  > +#define time_is_before_eq_jiffies(a) time_after_eq(jiffies, a)
>  > +
>  > +/* time_is_after_eq_jiffies(a) return true if a is after or equal to jiffies*/
>  > +#define time_is_after_eq_jiffies(a) time_before_eq(jiffies, a)
>  > +
>  > +/*
>  >   * Have the 32 bit jiffies value wrap 5 minutes after boot
>  >   * so jiffies wrap bugs show up earlier.
>  >   */
>  > --
>  > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>  > the body of a message to majordomo@vger.kernel.org
>  > More majordomo info at  http://vger.kernel.org/majordomo-info.html
>  > Please read the FAQ at  http://www.tux.org/lkml/
>
>
>

      reply	other threads:[~2008-03-11  4:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10  1:22 Dave Young
2008-03-11  3:17 ` KOSAKI Motohiro
2008-03-11  4:51   ` Dave Young [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=a8e1da0803102151y125f497x4d7fd57374c59b29@mail.gmail.com \
    --to=hidave.darkstar@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hannes@saeurebad.de \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH v3] Add time_is_after_jiffies and others which compare with jiffies' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).