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>] [day] [month] [year] [list]
Date:	Sat, 11 Feb 2012 14:08:06 -0500
From:	Gene Heskett <gene.heskett@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: OT question on top/htop/etc system monitors

Greetings all;

Users of the RTAI facility to run certain processes on a cpu core that has 
been isolated by the boot parameter 'isolcpus=n' command need to be able to 
confirm that the process so launched is indeed using x% of that cpu core.

There doesn't appear to be any facility in such as htop, to actually 
determine this usage.  In fact, if we taskset the whole linuxcnc (was emc 
till the lawyers wrote) gkrellm is the only utility that does show any 
usage of that isolated core.  Then of course its quite high because every 
thread in the program is running on that core.

Is the monitoring of an isolcpus defined core even possible?

And if possible, could it be added to htop so it displays the core that the 
RTAI threads are running on?

It would sure give us another tool to help optimize this application.

Thanks and Cheers, Gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://coyoteden.dyndns-free.com:85/gene>
We totally deny the allegations, and we're trying to identify the 
allegators.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ