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] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHmME9o0+9EKv=ErSUXQivkGoXamFJY3T_KETjf7=SG-FOB+WQ@mail.gmail.com>
Date:   Fri, 21 Jun 2019 17:07:32 +0200
From:   "Jason A. Donenfeld" <Jason@...c4.com>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 3/3] timekeeping: add missing _ns functions for coarse accessors

On Fri, Jun 21, 2019 at 4:58 PM Arnd Bergmann <arnd@...db.de> wrote:
> I care less about these since ktime_get_real_fast_ns() already
> exists. My preference would be leaving alons the _fast_ns()
> functions for now, but making everything else consistent instead.
>
> Thomas created the _fast_ns() accessors with a specific application
> in mind, and I suppose we don't really want them to be used much
> beyond that. I wonder if we should try to come up with a better
> name instead of "fast" that makes the purpose clearer and does
> not suggest that it's faster to read than the "coarse" version.

Oh shoot, I just submitted v3 having not seen this. Does v3's 4/4 look
fine, or shall I undo the _fast switcheroo and resubmit?

Jason

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ