linux-kernel - Re: [tip:tracing/core] ring-buffer benchmark: Run producer/consumer threads at nice +19

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: <1259072418.22249.1068.camel@gandalf.stny.rr.com>
Date:	Tue, 24 Nov 2009 09:20:18 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	mingo@...hat.com
Cc:	hpa@...or.com, linux-kernel@...r.kernel.org, fweisbec@...il.com,
	a.p.zijlstra@...llo.nl, efault@....de, tglx@...utronix.de,
	mingo@...e.hu, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:tracing/core] ring-buffer benchmark: Run
 producer/consumer threads at nice +19

On Tue, 2009-11-24 at 09:16 -0500, Steven Rostedt wrote:

> > Renice them to +19 to make them less intrusive.
> 
> Ingo, that is the point of a benchmark!
> 
> This module is not made to be run all the time. I know you do it for
> testing. But running it at lowest priority kills the reason this module
> was made in the first place!

Note, I first wrote this where the threads ran at SCHED_FIFO (but never
published it that way). I was afraid if something went wrong, it would
lock up the system. But still, it is a benchmark module. It is for
developers and analyzers only. Not for common users.

-- Steve


--
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/