linux-kernel - Re: [PATCH v4 3/3] tracing: add additional marks to signal very large delay

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]

Message-ID: <20141120085028.29efe8cf@gandalf.local.home>
Date:	Thu, 20 Nov 2014 08:50:28 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Namhyung Kim <namhyung@...nel.org>
Cc:	byungchul.park@....com, mingo@...hat.com,
	linux-kernel@...r.kernel.org, seungho1.park@....com,
	jolsa@...hat.com
Subject: Re: [PATCH v4 3/3] tracing: add additional marks to signal very
 large delay

On Thu, 20 Nov 2014 15:11:19 +0900
Namhyung Kim <namhyung@...nel.org> wrote:


> >> +	  '#' - greater than 1000 microsecond
> >> +	  '!' - greater than 100 microsecond
> >> +	  '+' - greater than 10 microsecond
> 
> I've noticed that it's now changed from 1 msec to 10 msec.  Is it okay?

Yeah, I didn't like the inconsistency between the two tracers, and not
only that, I  found the 1 microsecond mark rather useless. 10 is a much
better value. I don't think people will complain about this API change.

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