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: <2234BBB33B4B2048B28E3B3ACFC9795C01B834EB@CNBEEXC007.nsn-intra.net>
Date:	Wed, 24 Mar 2010 13:58:47 +0800
From:	"Zhu, Yijun (NSN - CN/Beijing)" <yijun.zhu@....com>
To:	"LKML" <linux-kernel@...r.kernel.org>,
	<linux-arch-owner@...r.kernel.org>
Subject: How to reserved all the CPU time for the private computing

Hi All:

Thank you very much firstly.
I have send the similar questions last time and I also search solutions
in the internet.

Scenario:
multi-core cpu, but only one of cores is running linux for control
plane, while others are running the private 100% computing

Solution:
The following steps are done:
1. Add the isolcpus opinion in the kernel command
2. The init thread only can run in the control CPU
3. disable all the local interrupt in the other CPUs/cores.

Result:
The system can be up, but NOT stable. Any system call may stuck the
shell(i.e  ping/chkconfig ). 

Question:
Could some give me some help/suggestion for the next steps?

Thanks a lot.
--
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