linux-kernel - Re: Context switch latency in tickless isolated CPU

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: <20160819123437.GE10121@twins.programming.kicks-ass.net>
Date:   Fri, 19 Aug 2016 14:34:37 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     GeHao Kang <kanghao0928@...il.com>
Cc:     Chris Metcalf <cmetcalf@...lanox.com>, fweisbec@...il.com,
        linux-api@...r.kernel.org, linux-kernel@...r.kernel.org,
        tglx@...utronix.de, mingo@...nel.org, paulmck@...ux.vnet.ibm.com
Subject: Re: Context switch latency in tickless isolated CPU

On Thu, Aug 18, 2016 at 11:25:00AM +0800, GeHao Kang wrote:

> Is the increased time fixed in each context switch? Because this increased time
> will be the latency of the real time application, we hope to confirm it.
> Thanks.

Why are you wanting to use nohz_full if you do syscalls?