From: Andi Kleen <andi@firstfloor.org>
To: torvalds@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: fallout of 16K stacks
Date: Tue, 8 Jul 2014 00:30:01 +0200 [thread overview]
Message-ID: <20140707223001.GD18735@two.firstfloor.org> (raw)
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
usually doesn't survive the night.
Do we need to strengthen the memory allocator to try
harder for 16K?
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: torvalds@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: fallout of 16K stacks
Date: Tue, 8 Jul 2014 00:30:01 +0200 [thread overview]
Message-ID: <20140707223001.GD18735@two.firstfloor.org> (raw)
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
usually doesn't survive the night.
Do we need to strengthen the memory allocator to try
harder for 16K?
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next reply other threads:[~2014-07-07 22:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 22:30 Andi Kleen [this message]
2014-07-07 22:30 ` fallout of 16K stacks Andi Kleen
2014-07-07 22:49 ` H. Peter Anvin
2014-07-07 22:49 ` H. Peter Anvin
2014-07-07 23:04 ` Andi Kleen
2014-07-07 23:04 ` Andi Kleen
2014-07-07 23:52 ` Linus Torvalds
2014-07-07 23:52 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140707223001.GD18735@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.