Prev: [PATCH -mmotm] pagemap: add #ifdefs CONFIG_HUGETLB_PAGE on code walking hugetlb vma
Next: perf: hard lockup when using perf-sched
From: Zhu, Yijun (NSN - CN/Beijing) on 24 Mar 2010 02:00
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(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH -mmotm] pagemap: add #ifdefs CONFIG_HUGETLB_PAGE on code walking hugetlb vma
Next: perf: hard lockup when using perf-sched