linux-kernel - Re: [PATCH] clockevents: Per cpu tick skew boot option

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: <alpine.LFD.2.02.1205081143510.6271@ionos>
Date:	Tue, 8 May 2012 11:44:26 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Mike Galbraith <mgalbraith@...e.de>
cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] clockevents: Per cpu tick skew boot option

On Tue, 8 May 2012, Mike Galbraith wrote:

> On Mon, 2012-05-07 at 21:17 +0200, Thomas Gleixner wrote: 
> > On Sun, 6 May 2012, Mike Galbraith wrote:
> > >  
> > > +	skew_tick=	[KNL] Offset the periodic timer tick per cpu to mitigate
> > > +			xtime_lock contention on larger systems.  Note: increases
> > > +			power consumption, and should only be enabled if running
> > > +			jitter sensitive (HPC/RT) workloads.
> > > +
> > 
> > The "=" is wrong as skew_tick should not take parameters. It's
> > disabled by default. So "skew_tick" simply enables it, right ?
> 
> Unless as I have RT set up, it's turned on by default, so '=' lets the
> user turn it back off.

Then the doc should say what's the parameter after the "+" is :)
--
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/