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]
Date:	Thu, 06 Oct 2011 12:22:24 +0530
From:	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
To:	Pavel Ivanov <paivanof@...il.com>
CC:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Full lockup when compiling kernel with "optimal" number of threads

On 10/06/2011 03:13 AM, Pavel Ivanov wrote:
> On Mon, Oct 3, 2011 at 5:39 AM, Srivatsa S. Bhat
> <srivatsa.bhat@...ux.vnet.ibm.com> wrote:
>> On 09/03/2011 09:04 AM, Pavel Ivanov wrote:
>>> Hi,
>>>
>>> I can reliably reproduce a complete machine lockup when compiling
>>> kernel sources with "make -j". After making some progress machine
>>> stops responding to anything (including CapsLock/NumLock switching or
>>> mouse moving) and after hard reboot nothing is left in kern.log or
>>> syslog. Only attaching a serial console gives me the following clues
>>> to what happens:
>>>
>> By the way "optimal" is supposed to be make -j <nr_cpus*2> isn't it?
>> IIRC, "maximal" refers to make -j
> 
> I'm sure I didn't make up that word "optimal" by myself. I took it
> from some documentation or internet, although now I can't find where I
> took it from. Wherever I look it says that -j is "unbounded" number of
> threads.
> 

I was referring to the terms used by kernbench.

-- 
Regards,
Srivatsa S. Bhat  <srivatsa.bhat@...ux.vnet.ibm.com>
Linux Technology Center,
IBM India Systems and Technology Lab
--
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