From: Lutz Vieweg <lvml@5t9.de>
To: Ying Han <yinghan@google.com>
Cc: Balbir Singh <balbir@linux.vnet.ibm.com>,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-mm@kvack.org
Subject: Re: "make -j" with memory.(memsw.)limit_in_bytes smaller than required -> livelock, even for unlimited processes
Date: Tue, 21 Jun 2011 18:19:15 +0200 [thread overview]
Message-ID: <4E00C483.5080302@5t9.de> (raw)
In-Reply-To: <BANLkTime3JN9-fAi3Lwx7UdXQo41eQh0iw@mail.gmail.com>
On 06/21/2011 06:01 PM, Ying Han wrote:
> The following patch might not be the root-cause of livelock, but
> should reduce the [kworker/*] in your case.
>
> From d1372da4d3c6f8051b5b1cf7b5e8b45a8094b388 Mon Sep 17 00:00:00 2001
>
> Can you give a try?
I will first need to move this test to a machine (like my Laptop)
that I can more aggressively reboot without disturbing the
developers on the shared hardware. Will do that asap.
> I don't know which kernel you are using in case
> you don't have this patched yet.
2.6.39.
5 out of 6 hunks in your patch apply to this version, 1 is rejected -
so I guess I should upgrade to a more recent kernel, first.
Would 2.6.39.1 be sufficient or would some non-release kernel
(from which git repository?) be required?
Regards,
Lutz Vieweg
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-06-21 16:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 14:51 "make -j" with memory.(memsw.)limit_in_bytes smaller than required -> livelock, even for unlimited processes Lutz Vieweg
2011-06-21 16:01 ` Ying Han
2011-06-21 16:19 ` Lutz Vieweg [this message]
2011-06-21 16:28 ` Ying Han
2011-06-21 16:35 ` Lutz Vieweg
2011-06-22 0:10 ` KAMEZAWA Hiroyuki
2011-06-22 1:06 ` KAMEZAWA Hiroyuki
2011-06-22 10:20 ` KAMEZAWA Hiroyuki
2011-06-22 14:37 ` Michal Hocko
2011-06-22 9:53 ` Lutz Vieweg
2011-06-23 6:13 ` KAMEZAWA Hiroyuki
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=4E00C483.5080302@5t9.de \
--to=lvml@5t9.de \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=yinghan@google.com \
/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.