linux-kernel - Re: [PATCH] hrtimer: add hrtimer_start

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 22 Jan 2015 20:35:24 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Olliver Schinagl <o.schinagl@...imaker.com>
cc:	linux-kernel@...r.kernel.org, Olliver Schinagl <oliver@...inagl.nl>
Subject: Re: [PATCH] hrtimer: add hrtimer_start_now()

On Thu, 22 Jan 2015, Olliver Schinagl wrote:
> On 22-01-15 12:01, Thomas Gleixner wrote:
> > Aside of that, what's wrong with doing:
> > 
> >        static const ktime_t ktime_zero = { .tv64 = 0 };
> > 
> >        hrtimer_start(timer, ktime_zero, HRTIMER_MODE_REL);
> I guess the same could be said for hrtimer_forward_now I suppose. It was just
> intended as a little helper, with emphasis on helper.

Well, no. htimer_forward_now() is mainly there to maintain a periodic
schedule which takes gaps into account.

I have nothing against the start_now() helper, but it's simpler and
less code with start relative than with abs and get_time().

Thanks,

	tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/