From: "KOSAKI Motohiro" <m-kosaki@ceres.dti.ne.jp>
To: "Lee Schermerhorn" <Lee.Schermerhorn@hp.com>
Cc: "Paul Menage" <menage@google.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Rik van Riel" <riel@redhat.com>,
"KAMEZAWA Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [BUG?] 2.6.25-rc[23]-mm1 cgroup list corruption under load with VM Scalability patches
Date: Thu, 20 Mar 2008 16:58:07 +0900 [thread overview]
Message-ID: <2f11576a0803200058k4ee85bf1se6abe272c496c39d@mail.gmail.com> (raw)
In-Reply-To: <1205863811.5032.26.camel@localhost>
Hi
CC'ed KAMEZAWA-san
> > > list_del corruption in cgroup_exit() on 16 cpu, 32GB ia64 NUMA platform.
> > >
> > > I've been seeing this for a while now, but we've had known problems
> > > [page leaks, ...] with the VM scalability series. Now the system
> > > appears to be running very well with these patches under stress loads
> > > that would hang it or cause OOM kill of tests with plenty of swap space
> > > left. Eventually, [after 40-45 minutes], I hit a list corruption in
> > > cgroup_exit().
> > >
> > > I can't say for sure that our patches aren't causing this, but I've been
> > > unable to keep the system up long enough under the stress load w/o the
> > > splitlru+noreclaim patches to hit the problem.
sorry for late responce, I don't notice this thread.
fujitsu guys investigated that problem too.
AFAIK this problem already fixed KAMEZAWA-san.
but I don't know that patch merged -mm or not.
kamezawa-san, please let us know its status?
next prev parent reply other threads:[~2008-03-20 7:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 19:37 Lee Schermerhorn
2008-03-05 21:09 ` Paul Menage
2008-03-18 18:10 ` Lee Schermerhorn
2008-03-20 7:58 ` KOSAKI Motohiro [this message]
2008-03-20 14:52 ` kamezawa.hiroyu
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=2f11576a0803200058k4ee85bf1se6abe272c496c39d@mail.gmail.com \
--to=m-kosaki@ceres.dti.ne.jp \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=riel@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®