On Mon, Jul 7, 2014 at 4:04 PM, Andi Kleen wrote:
>>
>> As in ENOMEM or does something worse happen?
>
> EAGAIN, then the workload stops. For an overnight stress
> test that's pretty catastrophic. It may have killed some stuff
> with the OOM killer too.
I don't think it's OOM.
We have long had t
On Mon, Jul 07, 2014 at 03:49:48PM -0700, H. Peter Anvin wrote:
> On 07/07/2014 03:30 PM, Andi Kleen wrote:
> >
> > Since the 16K stack change I noticed a number of problems with
> > my usual stress tests. They have a tendency to bomb out
> > because something cannot fork.
>
> As in ENOMEM or doe
On 07/07/2014 03:30 PM, Andi Kleen wrote:
>
> Since the 16K stack change I noticed a number of problems with
> my usual stress tests. They have a tendency to bomb out
> because something cannot fork.
As in ENOMEM or does something worse happen?
> - AIM7 on a dual socket socket system now cannot
Since the 16K stack change I noticed a number of problems with
my usual stress tests. They have a tendency to bomb out
because something cannot fork.
- AIM7 on a dual socket socket system now cannot reliably run
>1000 parallel jobs.
- LTP stress + memhog stress in parallel to something else
usua
4 matches
Mail list logo
